I don't think that I've got the time to make tests the next two weeks, but
I'll do that as soon as possible.
Regards,
Thorsten
-Ursprüngliche Nachricht-
Von: "Alan Stern" <[EMAIL PROTECTED]>
An: "Thorsten Wiedemer" <[EMAIL PROTECTED]>
Cc:
G
Hi !
> Yes, I'm playing around with some multi-threaded probing stuff right
> now. I've got PCI working pretty well now, see the -mm kernel for the
> patches if you want to test it out.
>
> However it's not going to directly translate over to the USB code, we
> have to limit probing to a per-devi
Hi !
Thanks for the quick answers !
> You shouldn't make timing measurements based on when things show up in
> /var/log/messages. That file is maintained by the syslog daemon, which
> does not necessarily add entries as soon as they are available. Instead
> you should use dmesg (there is a CONF
d the hotplug
environment were the same in both cases.
This is perhaps a stupid question, but is there a possibility to speed up
the connect handling (without rewriting the whole usb drivers ...) in the
newer kernel ?
Any hints are welcome.
Regards,
Thorsten
Hi list !
I'm developping a linux usb driver (kernel 2.6) to access a cypress fx2 and
a FPGA which is connected as FIFO Master to the fx2. I thought of using two
device files. One to read/write data from/to fx2 firmware and a second one
to pass/get data to/from the FPGA without firmware interventi
Hi list !
I wrote an usb driver on Suse 7.3 (2.4.10-4GB) which works quite fine.
When I compile this driver on a Suse 8.2 (2.4.20-4GB) and make "insmod", it
gives me the error "unresolved symbol schedule". I Googled a while and found
that the problem has to do with a change of kernel symbol "s
> > I tried this. I added the ioctl function to my driver. If I call this
> > ioctl with the registered device file opened, it works fine.
> > If I try to do this via usbfs (/proc/bus/usb/001/0xx), the open call
> > doesn't invoke the open function of my driver. Can someone give my a hint
> > what
Hi !
Sorry to disturb again ...
I think the las thread I started became accidently private.
[snip]
>> My first idea was doing this as a script. But how can I find the relation
>> between the device file minor number / name (registered in the device
>> driver) and the topology location ?
>> I th
Hi list !
This is my first post on this list.
My name is Thorsten Wiedemer, and I make my first steps in USB driver
development for linux.
We want to connect multiple USB devices to one host. These devices are
identical but have to receive different data, depending on their topological
location
