> What kind of device do you have?
A SmartCard reader. Are there allocated major:minor numbers for such devices
(as there are for scanners, for example)?
> > 3. If my driver should be able to manage more than one device, should I
> > register at init() or probe() all the entries? or do it only
Hi all --
Bryan "TheBS" Smith here with AVS (Linux-WLAN domain). There was a
recent set of cross-posts to our "linux-wlan-devel[oper]" list that I
might have rejected without proper review. We normally limit posting to
our "devel[oper]" list to subscribers only, because a good 20-30% of the
"su
Matt,
This was a point I tried to make but failed.
Not all SCB/SRB's are highmem tested but OEM's claim support.
This I tried to have BIO change to do highmen drop to the lowmem window
upon entry of the request and this would have prevent most form breaking,
but this did not seem to get warm acc
Jens --
Thanks for the info. It may have been discussed 'here' (tho, this is
crosposted to two different lists), but I've been focused on 2.4 bugs (one
more left!) and hadn't seen this item.
I think for the first 2.5 kernels, we'll o with your 'vaddr' line, but I
think that being able to set hi
No lock. Tho I think it lies when sent an ALLOW_MEDIUM_REMOVAL command.
But, since this is USB anyway, it can be yanked from the bus at any time.
Matt
On Mon, Dec 31, 2001 at 01:08:29PM +, Alan Cox wrote:
> > Not quite. The unit could be removed while mounted. The SCSI layer
> > doesn't k
Here's a patch for 2.4.17, functionally matching the pending patches
for 2.5, that adds EHCI and "high speed USB" support. It adds:
- updates to the TT support, so USB 2.0 hubs work somewhat
- basic "hcd" framework (will evolve more in 2.5)
- EHCI driver plugging into both the above
For those who have sent me patches, but didn't see them in this series,
don't worry, I still have a lot more to go. I just wanted to try to
send them in small batches, instead of flooding Linus with 20+ patches :)
thanks,
greg k-h
___
[EMAIL PROTECTE
Hi,
Here's a patch against 2.5.2-pre5 that adds the USB kl5kusb105 driver.
The driver was written by Utz-Uwe Haus. A patch to add the driver to
the build and the Configure.help entry will be sent later.
thanks,
greg k-h
diff -Nru a/drivers/usb/serial/kl5kusb105.c b/drivers/usb/serial/kl5kus
Hi,
Here's a patch against 2.5.2-pre5 that adds the USB ipaq driver.
The driver was written by Ganesh Varadarajan. A patch to add the driver
to the build and the Configure.help entry will be sent later.
thanks,
greg k-h
diff -Nru a/drivers/usb/serial/ipaq.c b/drivers/usb/serial/ipaq.c
--- /
Hi,
Here's a patch against 2.5.2-pre5 that cleans up the usbfs code to use
the vfs much better. It also removes the usbdev entries from the inode
and super_block structures.
thanks,
greg k-h
diff -Nru a/include/linux/fs.h b/include/linux/fs.h
--- a/include/linux/fs.hMon Dec 31 10:37
Hi,
Here's a patch against 2.5.2-pre5 that removes the
piso_packet_descriptor_t and purb_t typedefs from the usb.h file and
fixes all of the code that referenced these typedefs. It also makes the
FILL_*_URB macros use the usb_fill_*_urb inline functions.
thanks,
greg k-h
diff -Nru a/include
On Mon, Dec 31, 2001 at 11:14:18AM -0800, Miles Lane wrote:
>
> Why are you bothering to send stuff to Linus when he has explicitly
> stated that he isn't applying anything before the bio changes settle
> in.
That's why you don't see any USB updates in his tree recently :)
> That's why Dave st
On Mon, 2001-12-31 at 10:38, Greg KH wrote:
> Don't build USB stuff in his tree. It is not correct. I've been
> pushing the proper changes to the different maintainers (Alan, Marcelo,
> and Linus.)
>
> If you want to see (and get) the latest copy of the USB trees, go to:
> http://linuxusb
Don't build USB stuff in his tree. It is not correct. I've been
pushing the proper changes to the different maintainers (Alan, Marcelo,
and Linus.)
If you want to see (and get) the latest copy of the USB trees, go to:
http://linuxusb.bkbits.net/
thanks,
greg k-h
_
No :)
See my previous response.
greg k-h
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=athlon
-DKBUILD_BASENAME=kl5kusb105 -c -o kl5kusb105.o kl5kusb105.c
kl5kusb105.c:139: unknown field `needs_int
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=athlon
-DKBUILD_BASENAME=ipaq -c -o ipaq.o ipaq.c
ipaq.c:74: unknown field `needs_interrupt_in' specified in i
On Mon, Dec 31, 2001 at 10:29:42AM +0200, Amira Solomovici wrote:
> Hi,
>
> Thanks for your help.
>
> Assuming that the usb driver is written for kernel v2.4 and above, I suppose
> I can use the devfs and dynamic allocation of major and minor numbers
> instead of fixed minors.
No, you still ne
On Sun, Dec 30, 2001 at 03:58:46PM -0500, Burton W wrote:
> Hello. I got this oops while trying to get my USB Visor Handspring to sync
> with my Debian Woody box (running 2.4.18-pre1). I can reproduce this at
> will; it happens everytime pilot-xfer is getting done doing a list of my
> Visor's cont
> Not quite. The unit could be removed while mounted. The SCSI layer
> doesn't know that the media might have been changed. So, while START_UNIT
> is the SCSI layer's way of probing for media change, it's not the only way
> that such a thing can be detected.
The media has no lock then ?
I'd s
On Sun, Dec 30 2001, Matthew Dharm wrote:
> If it shouldn't be used, it should be removed from the structure to force
> people to change.
It will be soonish. Davem has practically finished this already.
> This is probably why usb-storage broke, and it wasn't obvious to me what
> went wrong.
It'
Hi,
Thanks for your help.
One small question I still have:
> You in the driver decide the minor.
If I use the DEVFS_FL_AUTO_DEVNUM flag in devfs_register(), can I still
control the minor given? Or is this given automatically as well?
Thanks,
Amira.
___
> 1. What's the difference between usbdevfs and devfs? Is there a way of
> searching the /proc/bus/usb directory for a file entry (driver) that manages
> a certain device (by checking its vendor and product id)?
Usbdevfs is a file system for getting information about usb devices and
user space dr
Hi,
Thanks for your help.
Assuming that the usb driver is written for kernel v2.4 and above, I suppose
I can use the devfs and dynamic allocation of major and minor numbers
instead of fixed minors.
I read some stuff about it, but since I'm new to Linux I still have a few
questions that I would
24 matches
Mail list logo
