Hi Stefan and Greg,
I'm glad to contact with you.
I'm quite a beginner of Linux Firewire subsystem (Juju) and the others
like PCI and USB. So it's hard for me to realize what Juju should be.
But I can rebuild Juju and test it with my devices and modules for which
I'm working. I'm pleased to te
On May 27 Greg Kroah-Hartman wrote:
> Why not pass it in the probe() function, like USB and PCI does? That
> way, if the driver wants to save it for that device, it can.
I will try that, probably at the weekend.
--
Stefan Richter
-=-===-= -=-= ===-=
http://arcgraph.de/sr/
--
To unsubscribe f
On Sun, May 26, 2013 at 11:35:13PM +0200, Stefan Richter wrote:
> I think your approach is sensible. There is of course just the little
> problem that firewire-core keeps the matching device_id table entry as a
> secret to itself. Therefore, struct ieee1394_device_id.driver_data is
> currently to
On May 26 Stefan Richter wrote:
> (Adding LKML and Greg KH, in case that there are general opinions about
> how a bus_type should work.)
>
> On May 26 Takashi Sakamoto wrote:
> > Hi all,
> >
> > I'm a newbile for Linux Firewire subsystem and not used to IEEE 1394 bus
> > programing in Linux.
> >
(Adding LKML and Greg KH, in case that there are general opinions about
how a bus_type should work.)
On May 26 Takashi Sakamoto wrote:
> Hi all,
>
> I'm a newbile for Linux Firewire subsystem and not used to IEEE 1394 bus
> programing in Linux.
> So I happy to get your advices.
>
> Currently I'm
5 matches
Mail list logo
