On Saturday 08 January 2005 14:51, Alan Stern wrote:
> ...
> I see you didn't have CONFIG_USB_STORAGE_DEBUG set when you ran this test.
Actually I did. I do not know what log level the USB debug messages were, but
the silly syslog did not capture them. Now I have set it to write all kernel
messa
Phil Dibowitz wrote:
Refreshed against my tree, and replacing "USB" with "Ours Technology" to
be a bit more clear, I get the following.
I was just following the entry below my addition (looks like a similar disk
with similar problem), which also says just "USB". Plus, the device descriptor
iManu
On Fri, 7 Jan 2005 18:29:26 +0100, "Oliver Neukum" <[EMAIL PROTECTED]>
said:
> Am Freitag, 7. Januar 2005 17:57 schrieb [EMAIL PROTECTED]:
> > On Thu, 6 Jan 2005 14:43:40 +0100, "Oliver Neukum" <[EMAIL PROTECTED]>
> > said:
> > > Am Donnerstag, 6. Januar 2005 15:39 schrieb [EMAIL PROTECTED]:
> > >
This patch brings up to date the driver with the current stable development
source. A bug with RTS not raising upon first open was fixed, Al Borcher's
circular write buffer from the pl2303 driver was implemented, and various
fixes/cleanups were made.
Signed-off-by: Lonnie Mendez <[EMAIL PROTEC
Miquel Vidal wrote:
It seems this Pentax camera is not conformant to the USB storage
specification (It does not like the INQUIRY command. So we must handle
this command of the SCSI layer ourselves.).
here you have a report:
http://www.qbik.ch/usb/devices/search_res.php?pattern=pentax
http://www.qbi
El sáb, 08-01-2005 a las 18:26, Alan Stern escribió:
> On Sat, 8 Jan 2005, Phil Dibowitz wrote:
>
> > Here - I couldn't make that patch you sent apply. Not sure why. I re-did
> > it by hand, and I've attached it. You also didn't put a Signed-off-by
> > line in your patch, so I added that for you
Am Samstag, 8. Januar 2005 22:36 schrieb David Brownell:
> On Saturday 08 January 2005 10:51 am, Oliver Neukum wrote:
> > Upon further reflection, in a statically compiled driver you know
> > you are taking over from yourself, already at compile time.
>
> Not true with the default swsusp "shutdown
Am Samstag, 8. Januar 2005 22:45 schrieb David Brownell:
> On Saturday 08 January 2005 12:09 pm, Alan Stern wrote:
>
> > Time to go look at those logs again...
>
> Another complication here is that a serial console will give a much more
> complete set of logs than "dmesg" after swsusp resumes ..
On Sat, 8 Jan 2005 13:28:37 -0800, David Brownell <[EMAIL PROTECTED]> wrote:
> > BTW, while working for this particular customer I did find a problem in
> > the 2.4 EHCI code that was particular to the MIPS platform (which is
> > what my customer is using.) In the structure ehci_qh, there is an
>
Hi guys.
I've just joined the list in the hope that I might be able to provide
some help in getting USB suspend/resume more reliable, or at least get
better understanding regarding what the issues are.
On Sun, 2005-01-09 at 05:46, Oliver Neukum wrote:
> Am Samstag, 8. Januar 2005 18:52 schrieb Al
On Saturday 08 January 2005 12:09 pm, Alan Stern wrote:
> Time to go look at those logs again...
Another complication here is that a serial console will give a much more
complete set of logs than "dmesg" after swsusp resumes ... below, I
summarize log contents, with CAPS SHOWING WHAT DMESG WILL
On Sat, 08 Jan 2005 12:07:44 -0600, Larry Schiefer <[EMAIL PROTECTED]> wrote:
> Thanks for the feedback. This probably isn't a question for you, but if
> someone were to back-merge this functionality, what are the chances the
> 2.4 kernel maintainers would allow it to be patched into the mainline
On Saturday 08 January 2005 10:51 am, Oliver Neukum wrote:
> Upon further reflection, in a statically compiled driver you know
> you are taking over from yourself, already at compile time.
Not true with the default swsusp "shutdown" method. In that case
you're quite possibly taking over from BIOS
On Saturday 08 January 2005 10:36 am, Larry Schiefer wrote:
>
> BTW, while working for this particular customer I did find a problem in
> the 2.4 EHCI code that was particular to the MIPS platform (which is
> what my customer is using.) In the structure ehci_qh, there is an
> atomic reference cou
On Sat, 8 Jan 2005, Oliver Neukum wrote:
> Am Samstag, 8. Januar 2005 18:52 schrieb Alan Stern:
>
> > Secondly, the startup kernel gets control of the machine. If the HCD is
> > compiled in, then it will grab the HC and reset it. (I would like to know
> > how to tell whether that step can be av
On Sat, 8 Jan 2005, Larry Schiefer wrote:
> Alan,
>
> Thanks for the feedback. This probably isn't a question for you, but if
> someone were to back-merge this functionality, what are the chances the
> 2.4 kernel maintainers would allow it to be patched into the mainline
> since it's not a bugfi
Hi!
After reading some posts in this list I realize there are quite some
problems with the VIA pci chips. I have one of those cards and i'm
trying to get it working. Hopefully my debug output might be of some
use to resolve this problem.
The card has two usb 2.0 ports.
# lspci -vv
***This is jus
Am Samstag, 8. Januar 2005 18:52 schrieb Alan Stern:
> Thirdly the memory image is restored and the driver in the image is
> running again. Now it may have to take control of the HC from the BIOS,
> from nobody (but after the HC may or may not have been reset), from its
> duplicate in the startup
Am Samstag, 8. Januar 2005 18:56 schrieb Alan Stern:
> On Sat, 8 Jan 2005, Oliver Neukum wrote:
>
> > Am Samstag, 8. Januar 2005 05:48 schrieb Alan Stern:
> > > Oliver, what happens if you run with CONFIG_USB_SUSPEND not set and apply
> > > the patch I wrote for Paul Ionescu in
> > >
> > > http:/
Am Samstag, 8. Januar 2005 18:52 schrieb Alan Stern:
> Secondly, the startup kernel gets control of the machine. If the HCD is
> compiled in, then it will grab the HC and reset it. (I would like to know
> how to tell whether that step can be avoided. There's a further
You can't. You only know
David,
Thanks for the additional input.
BTW, while working for this particular customer I did find a problem in
the 2.4 EHCI code that was particular to the MIPS platform (which is
what my customer is using.) In the structure ehci_qh, there is an
atomic reference counter, refcount. This structu
On Sat, 8 Jan 2005, Oliver Neukum wrote:
> Am Samstag, 8. Januar 2005 05:48 schrieb Alan Stern:
> > Oliver, what happens if you run with CONFIG_USB_SUSPEND not set and apply
> > the patch I wrote for Paul Ionescu in
> >
> > http://marc.theaimsgroup.com/?l=linux-usb-devel&m=110503079717138&w=2
>
Alan,
Thanks for the feedback. This probably isn't a question for you, but if
someone were to back-merge this functionality, what are the chances the
2.4 kernel maintainers would allow it to be patched into the mainline
since it's not a bugfix?
Thanks,
Larry
On Sat, 2005-01-08 at 12:00, Alan St
On Saturday 08 January 2005 7:45 am, Larry Schiefer wrote:
> 2. Is there something in the scatter-gather change that restricts it
> from being back-ported to the 2.4 kernel?
The main thing I'd worry about with respect to calling usb_sg_*() is
that for 2.4 HCDs the URB queueing isn't trustworthy .
David Brownell may have more to add, but here's my understanding...
On Sat, 8 Jan 2005, Larry Schiefer wrote:
> The Linux USB website had a short description about a change made to the
> USB 2.0 core and usb-storage drivers to support large I/O scatter lists
> at once. According to the descripti
On Sat, 8 Jan 2005, Oliver Neukum wrote:
> But I don't understand your line of reasoning. You are not taking
> over from the BIOS. You are taking over from yourself as the kernel
> has already initialised all devices once the image is read back.
It's a very tricky matter, and it depends on whethe
Hi,
Thanks for all the quick responses and help!
On Fri, Jan 07, 2005 at 01:41:27PM -0500, Craig Nadler wrote:
> The requested patch is as follows:
>...
I've applied the patch but sadly there has been no change.
>-Original Message-
>From: David Brownell [mailto:[EMAIL PROTECTED]
>Sent:
On Sat, 8 Jan 2005, Phil Dibowitz wrote:
> Here - I couldn't make that patch you sent apply. Not sure why. I re-did
> it by hand, and I've attached it. You also didn't put a Signed-off-by
> line in your patch, so I added that for you (I figure you want credit
> for your patch).
>
> This work f
Am Samstag, 8. Januar 2005 05:48 schrieb Alan Stern:
> Oliver, what happens if you run with CONFIG_USB_SUSPEND not set and apply
> the patch I wrote for Paul Ionescu in
>
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=110503079717138&w=2
No change.
Jan 8 11:49:39 macbeth kernel: Stopping t
All,
My name is Larry Schiefer and I am a software engineer for
Intelligraphics, Inc. We specialize in device driver and embedded
system development.
Currently, I am working for a client brining up MontaVista Linux on
their custom MIPS based platform. MV Linux runs a bit behind the latest
kerne
Am Samstag, 8. Januar 2005 05:48 schrieb Alan Stern:
> Oliver, what happens if you run with CONFIG_USB_SUSPEND not set and apply
> the patch I wrote for Paul Ionescu in
>
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=110503079717138&w=2
I'll apply it as soon as I am home.
But I don't unders
On Fri, Jan 07, 2005 at 09:47:43PM -0800, Greg KH wrote:
> ChangeSet 1.1938.444.33, 2004/12/22 13:50:21-08:00, [EMAIL PROTECTED]
>
> [PATCH] driver core: Fix up vesafb failure probing.
>
> bus.c file invokes a probe callback for most devices in a list, then checks
> for -ENODEV return ("no such d
Phil Dibowitz wrote:
Miquel Vidal wrote:
El dom, 02-01-2005 a las 07:47, Phil Dibowitz escribió:
Miquel Vidal wrote:
Hi All,
The change below in unusual_devs entries is needed to get the new
Pentax
SLR *ist DS camera working.
Can you please include the output of "cat /proc/bus/usb/devices" ?
Th
Daniel Drake wrote:
This "Ours Technology" device incorrectly reports 100% residue on
transferred data.
Refreshed against my tree, and replacing "USB" with "Ours Technology" to
be a bit more clear, I get the following.
--
Phil Dibowitz [EMAIL PROTECTED]
Freeware and T
34 matches
Mail list logo
