Posts
79
Following
28
Followers
25
A maintainer of Linux FireWire subsystem and ALSA firewire stack.
http://ieee1394.docs.kernel.org/
https://github.com/takaswie/linux-firewire-dkms/
takaswie

Takashi Sakamoto (坂本 貴史)

Enjoy weekend!
0
0
1
takaswie

Takashi Sakamoto (坂本 貴史)

Edited 2 years ago
For the next release, I will prepare environment to use fup tool since debian developers prefer to have fixed location of source tar ball.
0
0
1
takaswie

Takashi Sakamoto (坂本 貴史)

linux-firewire-utils version 0.5.0 release

You can download the new release from the following URL:
https://git.kernel.org/pub/scm/utils/ieee1394/linux-firewire-utils.git/tag/?h=v0.5.0

This marks the first release since the project was hosted at
git.kernel.org[1]. In this release, crpp tool has been removed due to
Python 2 and license issues. Instead, a new tool called
config-rom-pretty-printer has been added as an alternate. This tool is
implemented in C language and closely resembles the output of the original
tool, capturing approximately 80% of its functionality. However some
legacy functions, such as the firecontrol parser, have been dropped.

The original tool is maintained by Clemens Ladisch and hosted on
github.com[2]. However there has been no activity on the repository in
recent years[3]. As a result, the project was forked to git.kernel.org and
is now maintained by Takashi Sakamoto.

I would like to take this opportunity to express my gratitude for Clemens
Ladisch's work on the original tool. I am delighted to be able to release
an updated version after 8 years of silence.

[1] https://git.kernel.org/pub/scm/utils/ieee1394/linux-firewire-utils.git/
[2] https://github.com/cladisch/linux-firewire-utils/
[3] https://github.com/cladisch/linux-firewire-utils/pull/1
0
3
2
takaswie

Takashi Sakamoto (坂本 貴史)

By the way, let me enjoy this Friday night.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

And I have no devices for which the tool supports protocols, sigh.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

I wonder why I should rewrite a Python 2 script by C language... phew: https://git.kernel.org/pub/scm/utils/ieee1394/linux-firewire-utils.git/commit/?id=9164a62d5e273
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

I was so careless due to the load to prepare version 0.1.0 release...
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Reply to
@broonie Oops. I apologize that I forgot to add you to CC list... Now I resent it with CC including you. Thanks for your check.
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Hi @broonie . I see your name in the history of linux-next repository and wonder how many bodies you have. You may be master of ninja, hehe.

By the way, I would like to add linux1394 upstream into linux-next integration, while the procedure is still unclear. A few days ago I sent to Stephen Rothwell C.C.ed to you, while got no reply. For next merge window coming up, it is convenient to me to check changes of linux1394 in linux-next integration. It is helpful to get any of your advices.
1
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

snd-firewire-ctl-services 0.1.0 released https://lore.kernel.org/alsa-devel/20230419084401.GA659018@workstation/T/#u
0
0
1
takaswie

Takashi Sakamoto (坂本 貴史)

I got tired to upload 12 crates to crates.io: https://crates.io/teams/github:alsa-project:gobject-introspection?sort=recent-updates
0
0
1
takaswie

Takashi Sakamoto (坂本 貴史)

Reply to @monsieuricon
@monsieuricon Exactly. I overlooked it, sorry. I always get less help for my work since IEEE 1394 is enough legacy and people are going to forget it. So I'm pretty happy to receive your help, thanks!
0
0
1
takaswie

Takashi Sakamoto (坂本 貴史)

Hi @monsieuricon. I sent my request to you for my access permissions to some repositories relevant to FireWire subsystem, and waiting mostly one month. Now I'm investigating to create new repository dedicated to linux-next integration since I have less weeks for next merge window than I expected, but if my access will grant soon, I'm pleased to use it. Should I wait for another couple of weeks or not?
1
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Reply to
@wagi @rostedt Indeed. I overlooked that Meson supports Solaris. Thanks for your correction. https://mesonbuild.com/Reference-tables.html#operating-system-names
0
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Reply to
@wagi @rostedt I respect the choice to cover the platforms such as Solaris, HP-UX, which meson build system does not support :D
1
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Reply to @rostedt
@rostedt It sounds reasonable. I guess that gettext/libintl support can be removed as well just by removal of gettext prefix.
Anyway, it is my pleasure that the patch takes you away from the hell.
0
0
2
takaswie

Takashi Sakamoto (坂本 貴史)

Reply to @rostedt
@rostedt Okay. I'm not so good at build environment for ChromeOS, but successfully build it by meson in Ubuntu 22.10.

https://github.com/takaswie/ureadahead/commits/topic/meson-build

I need to backport libnih package from https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/libnih/1.0.3-12build1/libnih_1.0.3-12build1.dsc, since it is outdated nowadays.

Cheers.
1
0
1
takaswie

Takashi Sakamoto (坂本 貴史)

Reply to @rostedt
@rostedt I'll take a look at https://github.com/rostedt/ureadahead.
1
0
0
takaswie

Takashi Sakamoto (坂本 貴史)

Reply to @rostedt
@rostedt Indeed. I shifted from GNU autotools to meson build system several years ago for libraries I maintain. I keep more time to have a beer instead of complicated macros.
1
0
1
takaswie

Takashi Sakamoto (坂本 貴史)

Linux kernel prepatch version 6.3 is out. It provides new function to ALSA fireface driver to handle knob control event for RME Fireface 400 (launched 2007, yes!).

I upload new version of libhitaki and Rust hitaki-sys/hitaki crates:

- https://github.com/alsa-project/libhitaki/releases/tag/v0.2.0
- https://github.com/alsa-project/hitaki-rs/releases/tag/v0.3.0
0
0
0
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: