All,
I'm trying to get any/all endian issues worked out of the asix driver so
I can be certain that it works on any platform but due to lack of access
to any big-endian hardware and lack of expertise with endian-issues, I
need some help.
Based on reports, AX88172 (older USB 2.0 Ethernet chip) devi
On Tue, Jan 30, 2007 at 06:33:43PM -0500, Rick Scott wrote:
> On Tue, 2007-01-30 at 05:05 -0500, Chris Frey wrote:
> > On Mon, Jan 29, 2007 at 05:21:39PM -0800, Greg KH wrote:
> > > Also, would it make sense to provide a userspace "pipe" to this device,
> > > so that the userspace tools can just op
Hi,
On Tue, Jan 30, 2007 at 03:31:24PM -0500, Alan Stern wrote:
> > next test:
> > http://userweb.kernel.org/~brodo/pre-insert
> > => added device 2
> > http://userweb.kernel.org/~brodo/post-insert
>
> These were all done with the controller supposedly suspended, right?
Yes.
> But
> they all s
On Tue, Jan 30, 2007 at 06:33:43PM -0500, Rick Scott wrote:
> In the end, I would like to be able to
> "cat to retrieve my pin, similarly to set new entries. In other
> words, treat the various databases like a filesystem that you could
> browse.
It is an interesting idea to make the databases av
On Tue, 2007-01-30 at 05:05 -0500, Chris Frey wrote:
> On Mon, Jan 29, 2007 at 05:21:39PM -0800, Greg KH wrote:
> > Also, would it make sense to provide a userspace "pipe" to this device,
> > so that the userspace tools can just open a device node, instead of
> > messing around with usbfs?
I would
On Tue, 30 Jan 2007, Oleg Verych wrote:
> > > So, if i will quickly invent `wc' (working configuration ;) module
> > > parameter for A driver, near vID:dID, i will not have any luck getting it
> > > changed in USB-Core,
> >
> > Getting _what_ changed in usbcore? What does "it" refer to? The 'wc
On Tue, Jan 30, 2007 at 11:07:35AM -0500, Alan Stern wrote:
> On Tue, 30 Jan 2007, Oleg Verych wrote:
>
> > > > What if one-prupose device, like ti-usb-serial require its one operation
> > > > in different setup, and driver's author know it? I would like to have
> > > > such _option_, as device dr
On Tue, 30 Jan 2007, Dominik Brodowski wrote:
> > Try running this test again, with CONFIG_USB_DEBUG turned on. After
> > plugging in a new device, make a copy of
> >
> > /sys/class/usb_host/usb_host1/registers
> >
> > and post it. Ditto for unplugging an existing device.
>
> http://user
On Tue, 30 Jan 2007, Oliver Neukum wrote:
> If calling wake_up() in suspend() is not a problem, why is it problematic
> in resume(). Does ordinary swsusp allow that?
I thought it did. For instance, usbcore can call wake_up() on khubd
during resume. On the other hand, I have seen peculiar thing
Hi,
On Tue, Jan 30, 2007 at 10:50:19AM -0500, Alan Stern wrote:
> On Mon, 29 Jan 2007, Dominik Brodowski wrote:
>
> > Allright, done some more debugging:
> > - using my patch with your fix, devices which are already plugged in when
> > the STS_FLR exception occurs continue to work
> > - however
Am Dienstag, 30. Januar 2007 19:16 schrieb Alan Stern:
> On Tue, 30 Jan 2007, Oliver Neukum wrote:
[..]
> > Furthermore, what about input? It seems to me that it also can call
> > wake_up()?
>
> You mean the control-IN queue? Same thing: either stop the queue or wait
> for it to drain.
No,
On Tue, 30 Jan 2007, Oliver Neukum wrote:
> > Do you really need to do all this? Shouldn't it be true, when you first
> > do the suspend, that all the I/O queues are empty? And since all tasks
> > are frozen and class drivers are suspended, no more I/O entries can be
> > created?
>
> It is impo
Le Monday 29 January 2007 19:50, Thierry Herbelot a écrit :
> Hello,
>
> I'm writing a USB device driver for a high-data rate device, for which I
> would like to use isochronous transfers (I already have working bulk
> transfers), but I can't get the expected (very high) data bandwidth.
>
> The sit
On Tuesday 30 January 2007 8:28 am, Alan Stern wrote:
>Shouldn't it be true, when you first
> do the suspend, that all the I/O queues are empty?
Actually, no. That's a gap in the Linux-PM framework: there's no way
to shut down tasks cleanly before starting the driver suspend sequence.
On Sat, 27 Jan 2007, Soeren Sonnenburg wrote:
> Dear all,
>
> I am trying to use a P990 phone in via mass storage under linux. I was
> able to copy data to/from the phone without trouble under winxp but
> receive millions of I/O errors (see below (*), basically on any sector).
> As this was also
On Tue, 2007-01-30 at 13:33 +0800, Dave Liu wrote:
> David,
> I have the other LINKSYS USB200M NIC adapter, which chipset is AX88172
> and PHY RTL8201. I can ping successfully with it in linux-2.6.20-rc6 on
> big-endian system, I noticed the AX88772 have on-chip PHY inside. so I
> feel the problem
Am Dienstag, 30. Januar 2007 17:28 schrieb Alan Stern:
> On Tue, 30 Jan 2007, Jiri Kosina wrote:
>
> > On Mon, 29 Jan 2007, Oliver Neukum wrote:
> >
> > > > thanks, I think that basically killing output URBs is a good thing to
> > > > do,
> > > I've looked further and the control URB will have t
On Sat, 27 Jan 2007, Dirk Eddelbuettel wrote:
> | > I doubt that. I'd say this new-ish (May 2006) model is 'different'.
> | > We have two of these Treo 700p (from Sprint) here, and they both
> | > behave identically:
> | >
> | > 1) they fail with current 'default' 2.6.x kernels from Debian testi
On Tue, 30 Jan 2007, Jiri Kosina wrote:
> On Mon, 29 Jan 2007, Oliver Neukum wrote:
>
> > > thanks, I think that basically killing output URBs is a good thing to do,
> > I've looked further and the control URB will have to die, too.
>
> Correct.
>
> > > however the resuming will need some more
On Mon, 29 Jan 2007, Oliver Neukum wrote:
> > thanks, I think that basically killing output URBs is a good thing to do,
> I've looked further and the control URB will have to die, too.
Correct.
> > however the resuming will need some more thinking. What are all the
> > scenarios you can see tha
On Tue, 30 Jan 2007, Oleg Verych wrote:
> > > What if one-prupose device, like ti-usb-serial require its one operation
> > > in different setup, and driver's author know it? I would like to have
> > > such _option_, as device driver _have_ option to choose device it can
> > > talk to -- ID tables.
On Mon, 29 Jan 2007, Jiri Kosina wrote:
> > > > > I've noticed that this patch is not in 2.6.20-rc1. Could you
> > > > > please comment on what is wrong with it / whether it will ever
> > > > > have a chance to be accepted in the way it is done ?
> > > > It's in my queue right now, sorry. I'll
On Mon, 29 Jan 2007, Dominik Brodowski wrote:
> Allright, done some more debugging:
> - using my patch with your fix, devices which are already plugged in when
> the STS_FLR exception occurs continue to work
> - however, new devices which are plugged in, or devices which are removed,
> (unless
This patch (as845) cleans up some fallout from the removal of the
usbcore bandwidth machinery.
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
---
Note that Andrew Morton has already applied the first hunk to the -mm
tree.
Alan Stern
Index: usb-2.6/drivers/isdn/gigaset/bas-gigaset.c
===
On Mon, Jan 29, 2007 at 05:21:39PM -0800, Greg KH wrote:
> Also, would it make sense to provide a userspace "pipe" to this device,
> so that the userspace tools can just open a device node, instead of
> messing around with usbfs?
Barry is intended to be a userspace library for accessing the Blackb
25 matches
Mail list logo
