On Fri, Jan 27, 2006 at 10:59:35PM -0500, Alan Stern wrote:
>On Fri, 27 Jan 2006, John Gruenenfelder wrote:
>
>> I applied the patch and rebooted with the new kernel. Unfortunately, it does
>> not seem to have made any difference as the external HD is never detected.
>>
>> When recompiling the ke
On Fri, 27 Jan 2006, John Gruenenfelder wrote:
> On Fri, Jan 27, 2006 at 10:15:47AM -0500, Alan Stern wrote:
> >On Thu, 26 Jan 2006, John Gruenenfelder wrote:
> >
> >> This is almost exactly the error I am seeing. I wrote a longish email
> >> about
> >> it to the list yesterday including my dmes
The email was deleted by system policy.
Attached file might be containing virus.
Connection From: 127.0.0.1
From: linux-usb-devel@lists.sourceforge.net
To: [EMAIL PROTECTED]
Date: Sat, 28 Jan 2006 12:31:50 +0900
Subject: Fwd: image.jpg
--- Scan information follows ---
Virus Name: [EMAIL PROTECTE
On Friday 27 January 2006 3:38 pm, Micah Dowty wrote:
> If usbfs really does need to verify that packets
> are correct as per the spec, it should be checking this against
> the endpoint's maximum packet size.
Actually those checks should live in the main urb submit paths,
leaving HCDs to tes
Greg KH wrote:
Devices like that surely never passed the usb.org test suite, right?
And as such, should not be able to display the USB.org logos, and
probably not work very well on any operating system...
Well, most USB devices are developed and tested only on Windows... and
I'm sure we all kno
On Fri, Jan 27, 2006 at 03:38:51PM -0800, Micah Dowty wrote:
> 1. usbfs seems to be the last thing to be updated when new
>specifications are released. Current usbfs code still doesn't
>allow full USB 2 high-speed support- how long will it take
>to make sure its arbitrary limits are cle
On Fri, Jan 27, 2006 at 10:15:47AM -0500, Alan Stern wrote:
>On Thu, 26 Jan 2006, John Gruenenfelder wrote:
>
>> This is almost exactly the error I am seeing. I wrote a longish email about
>> it to the list yesterday including my dmesg output and kernel .config file.
>>
>> One important thing I f
The 2k figure comes from the maximum size you can represent in
the wMaxPacketSize field of an isochronous endpoint descriptor.
Admittedly, this isn't really correct in either of the cases I
can picture. If usbfs really does need to verify that packets
are correct as per the spec, it should be chec
I guess I'm misunderstanding the purpose of these arbitrary limits
in usbfs. I had assumed that they weren't intended to enforce the
USB spec, but just to avoid allowing userspace processes to allocate
unreasonable amounts of unpaged memory.
--Micah
David Brownell wrote:
On Friday 27 January 20
On Friday 27 January 2006 2:09 pm, Micah Dowty wrote:
> This patch bumps usbfs' arbitrary limit on control URB buffer size
> up from one page to two pages. This is necessary to support devices
> that require control requests with a full 4096 bytes of data, since
> the URB buffer must also include 8
On Friday 27 January 2006 2:19 pm, Micah Dowty wrote:
> The usbfs code path for submitting Isochronous URBs still limits
> each packet to 1k. This may have been appropriate for USB 1.1, but
> high-speed devices sending multiple physical packets per microframe
> may require a much larger "packet" si
On Wed, Jan 25, 2006, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
> The usbfs is basically an equivalent of iopl and mmap(/dev/mem).
> Pushing applications in that direction is deeply troubling for me.
How so?
I'll be the first to admit that usbfs isn't exactly pretty, but it
certainly doesn't have t
On Fri, Jan 27, 2006 at 01:06:30AM +0100, Helge Hafting wrote:
> There seems to be a usb printer problem in 2.6.16-rc1 (amd64)
>
> I can print a page or two of graphichs (A4 maps), and then
> my syslog fills up with these:
> kernel: drivers/usb/class/usblp.c: usblp0: error -19 reading printer sta
On Wed, Jan 25, 2006 at 10:33:56PM -0800, Pete Zaitcev wrote:
> On Wed, 25 Jan 2006 21:50:02 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
>
> > Good new is, next version of pilot-link (or possibly this version)
> > accesses the device through libusb/usbfs, and doesn't touch the kernel
> > driver at a
The usbfs code path for submitting Isochronous URBs still limits
each packet to 1k. This may have been appropriate for USB 1.1, but
high-speed devices sending multiple physical packets per microframe
may require a much larger "packet" size. This increases the limit
to 6144, sufficient for three 2k
This patch bumps usbfs' arbitrary limit on control URB buffer size
up from one page to two pages. This is necessary to support devices
that require control requests with a full 4096 bytes of data, since
the URB buffer must also include 8 bytes for the SETUP packet.
Signed-off-by: Micah Dowty <[EM
Daniel Mack wrote:
>
> On Jan 27, 2006, at 10:23 PM, David Brownell wrote:
>
>> I pointed this out to Philips a while back, but they didn't
>> seem to believe me. They may well have some serious legal
>> mis-understandings going over there.
>
>
> They can still hand out some piece of code to y
On Friday 27 January 2006 08:38, Ulrich Windl wrote:
> (Note: For SuSE's 10.0 kernel 2.6.13-15.7-default I have the problem
> with ehci_hcd on a USB 2.0 device: The devices also seem to "not
> accept the address", and when I unload the ehci_hcd module, the
> device successfully connects as USB1. Bu
On Fri, Jan 27, 2006 at 10:44:09PM +0100, Daniel Mack wrote:
>
> On Jan 27, 2006, at 10:23 PM, David Brownell wrote:
>
> >I pointed this out to Philips a while back, but they didn't
> >seem to believe me. They may well have some serious legal
> >mis-understandings going over there.
>
> They can
On Friday 27 January 2006 12:48 pm, Greg KH wrote:
>
> You can't write a proprietary Linux USB host controller driver for
> recent kernel versions, so this must be wrong.
I pointed this out to Philips a while back, but they didn't
seem to believe me. They may well have some serious legal
mis-und
On Jan 27, 2006, at 10:23 PM, David Brownell wrote:
I pointed this out to Philips a while back, but they didn't
seem to believe me. They may well have some serious legal
mis-understandings going over there.
They can still hand out some piece of code to you, show you that
their hardware works
On Fri, Jan 27, 2006 at 11:53:07AM -0800, dfoley wrote:
> >> I generally have it working on our hardware but not without problems and
> >> have challenges getting support from Philips.
> >
> > Which licence did Philips use? Would it be possible to put that driver
> > into the CVS so more people c
Daniel Mack wrote:
> Hi dfoley,
>
>> I use this chip in a project as well.
>> We got drivers from Philips for 2.6.9 - pci.
>
>
> Interesting. What do you mean with 'pci'? I chose that chips just because
> I do *not* have a PCI bus in this setup?
>
Your are correct, but Philips has a PCI card w
On Sat, 28 Jan 2006 08:40:18 +1300, Reuben Farrelly <[EMAIL PROTECTED]> wrote:
> direction to fixing this, perhaps something more like ":00:1d.7 EHCI:
> BIOS
> handoff failed (BIOS bug? Try disabling legacy USB support in BIOS if it is
> enabled)"
I thought about this. However it seems th
On 28/01/2006 6:49 a.m., Pete Zaitcev wrote:
On Fri, 27 Jan 2006 09:27:20 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
How about just disabling USB legacy support in the bios completly?
Unless you have a USB keyboard that you need for a bootloader screen or
BIOS configuration, that's the recomme
On Fri, 27 Jan 2006 09:27:20 -0800, Greg KH <[EMAIL PROTECTED]> wrote:
> How about just disabling USB legacy support in the bios completly?
> Unless you have a USB keyboard that you need for a bootloader screen or
> BIOS configuration, that's the recommended setting (due to all of the
> horrible B
On Sat, Jan 28, 2006 at 01:46:20AM +1300, Reuben Farrelly wrote:
>
>
> On 26/01/2006 6:39 p.m., Greg KH wrote:
> >On Wed, Jan 25, 2006 at 11:44:14PM +1300, Reuben Farrelly wrote:
> >>
> >>On 25/01/2006 8:24 p.m., Andrew Morton wrote:
> >>>http://www.kernel.org/pub/linux/kernel/people/akpm/patches
[Moved this thread to linux-usb-devel, where it now belongs]
On Fri, 27 Jan 2006, Igor Yakushin wrote:
> The results of the tests are enclosed together with the usb.py script that is
> used to create a big
> file whose name is given on a command line.
> No copying between USB and local disk. The
On Fri, 27 Jan 2006, Ulrich Windl wrote:
> Hello,
>
> I wanted to report a problem with Linux kernel 2.6.15.1 and uhci_hcd for USB1
> on
> an Shuttle AV11 board (VIA Apollo chipset, P III, 700MHz): An USB device
> (connected already when the kernel booted) was not accepted ("device not
> acce
On Thu, 26 Jan 2006, John Gruenenfelder wrote:
> This is almost exactly the error I am seeing. I wrote a longish email about
> it to the list yesterday including my dmesg output and kernel .config file.
>
> One important thing I found was that the external device I was using (a
> harddrive enclo
Hi dfoley,
I use this chip in a project as well.
We got drivers from Philips for 2.6.9 - pci.
Interesting. What do you mean with 'pci'? I chose that chips just
because
I do *not* have a PCI bus in this setup?
I generally have it working on our hardware but not without
problems and
have
On 26/01/2006 6:39 p.m., Greg KH wrote:
On Wed, Jan 25, 2006 at 11:44:14PM +1300, Reuben Farrelly wrote:
On 25/01/2006 8:24 p.m., Andrew Morton wrote:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc1/2.6.16-rc1-mm3/
- Dropped the timekeeping patch series due to a co
32 matches
Mail list logo
