Hello Folks, I upgraded to FC2 recently and immediately ran into USB
problems that I had never encountered previously, the USB being very
reliable on earlier RH releases.
On kernel 2.6.5 (the kernel that came with the dist. CDs) USB was
extremely flakey with my Zip drive and, particularly, the HD
On Thu, Aug 05, 2004 at 08:09:19PM -0700, David Brownell wrote:
> Keeps implementation details out of host and peripheral
> side USB controller drivers ... needed for some upcoming
> merges (which may come first through the OMAP tree).
>
> Please merge.
Applied, thanks.
greg k-h
--
Keeps implementation details out of host and peripheral
side USB controller drivers ... needed for some upcoming
merges (which may come first through the OMAP tree).
Please merge.
- Dave
Hardware implementing USB-OTG needs to use an OTG controller and/or
transceiver driver to switch the Mini-AB co
here you have the info I have:
- Motherboard: nforce2
You have dmesg and lspci.
- -268-rc2 don't work.
- -works is 268-rc2-mmX (without the bk-usb.patch), so it works.
when it works, I have boot ehci and ohci (and I can use my usb-pen and my
camera), but when it don't work, I only have ohci, so
On Tue, Aug 03, 2004 at 12:19:25PM +0200, Florian Echtler wrote:
> Next iteration, now hopefully with all bugs and ugliness issues fixed.
Oh, so close, only a few minor issues:
> diff --unified --recursive --new-file linux-2.6.7/drivers/usb/Makefile
> linux/drivers/usb/Makefile
> --- linux-2.6.7
Hello everyone,
While running vanilla 2.4.26 on Motion Computing M1300 Tablet, I
encountered the following problem: if a key is pressed several times on
USB keyboard during kernel boot, boot locks up at EHCI driver init. Boot
succeeds normally if keyboard remains untouched.
After investigating
On Tue, Aug 03, 2004 at 02:18:09PM -0700, David Brownell wrote:
> Some one-liners sent to me yesterday, plus support for the new
> usb_gadget_disconnect() and usb_gadget_connect() softconnect calls.
Applied, thanks.
greg k-h
---
This SF.Net em
On Tue, Aug 03, 2004 at 02:28:03PM -0400, Alan Stern wrote:
> Greg:
>
> This patch is a repeat of as335, as described in
>
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=108861892700869&w=2
>
> but updated to match the current source. It should be non-controversial;
> it has nothing to do
On Tue, Aug 03, 2004 at 02:10:51PM -0700, David Brownell wrote:
> This should help EHCI work better on some boards where
> the BIOS support is buggy.
Applied, thanks.
greg k-h
---
This SF.Net email is sponsored by OSTG. Have you noticed the ch
On Tue, Aug 03, 2004 at 02:25:26PM -0400, Alan Stern wrote:
> Greg:
>
> This patch is a repeat of as331 as described in
>
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=108811725219677&w=2
>
> It has been updated slightly to match the current source. It should be
> non-controversial; it h
On Wed, Aug 04, 2004 at 11:01:44AM +0200, Duncan Sands wrote:
> usb_reset_device takes hdev->serialize. However, hub_reset is
> (only) called by hub_events, which already holds the lock. Thanks
> to Tyler Nielsen for the bug report and helpful backtrace.
Applied, thanks.
greg k-h
On Tue, Aug 03, 2004 at 11:01:42AM +0200, Luca Risolia wrote:
> Oops, one more.
>
> Greg, please apply this after the previous patch.
>
> Signed-off-by: Luca Risolia <[EMAIL PROTECTED]>
Applied, thanks.
greg k-h
---
This SF.Net email is spon
On Tue, Aug 03, 2004 at 10:34:36AM +0200, Luca Risolia wrote:
> This patch brings the driver up to the first stable version.
>
> Changes:
>
> * Remove "redblue" entry under /sys
> * Better coding style for comments
> * Fix the image downscaling factor calculation
> * Fix default color settings fo
On Thursday 05 August 2004 06:13, Ian Molton wrote:
> I now can get interrupts frmo the device, so its *nearly* there.
You forgot the smiley face. :)
> My one problem is that Im chainbooting from winCE so I cant be sure the
> controller hasnt been futzed with.
>
> The obvious problem to attac
Thanks for the info Kevin, but the issue still persists for me in 2.6.8-rc3-mm1.
On Thu, 5 Aug 2004 11:08:18 -0700, Kevin O'Shea <[EMAIL PROTECTED]> wrote:
> Just thought you guys would like to know I had this same problem since
> 2.6.7-mm6, but it is now fixed for me in 2.6.8-rc3-mm1.
>
> I have
Just thought you guys would like to know I had this same problem since
2.6.7-mm6, but it is now fixed for me in 2.6.8-rc3-mm1.
I have an intel 865PE chipset.
---
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com,
Thanks for the reply David, but where exactly does this leave me and
the others experiencing this problem? Is there any more information I
can provide that might help? Any possible solutions, patches, etc?
On Thu, 5 Aug 2004 08:34:27 -0700, David Brownell <[EMAIL PROTECTED]> wrote:
> On Wednesda
On Thursday 05 August 2004 06:39, Olaf Hering wrote:
> On Thu, Jul 15, Olaf Hering wrote:
>
> > On Tue, Jul 13, David Brownell wrote:
> >
> > > Instead, how about: (a) longer timeout, 5 seconds to match OHCI's
> > > absurdly long default there; (b) change that "handoff failed" message
> > > to
On Thursday 05 August 2004 00:24, Norbert Preining wrote:
> Hi USB Gurus!
>
> 2.6.8-rc2-mm2
>
> It just happened to me that my X stopped working (all frozen) while
> syncing my palm. Sysrq/syslog brought forth:
>
> vmunix: bad: scheduling while atomic!
> vmunix: [] schedule+0x3d8/0x3e0
> vmunix
On Wednesday 04 August 2004 23:51, Norbert Preining wrote:
> Hi David!
>
> On Mit, 04 Aug 2004, David Brownell wrote:
> > Not clear how to read that stack; if it's usbdev_open()
> > that's making the trouble, lock_kernel() is blocked.
> > But that doesn't quite make sense to me. Sorry!
>
> So wh
On Wednesday 04 August 2004 20:57, Michael Guterl wrote:
> Attached are my dmesg's from each kernel, each time I booted fully,
> then plugged the USB keyboard in, and then the USB mouse. My kernel
> config is also attached, along with the output of lspci -v, (David
> Brownell mentioned "lspci -w"
A virus was found in a message sent by this
account.
--- Scan information follows ---
Result: Virus Detected
Virus Name: [EMAIL PROTECTED]
File Attachment: msg.exe
Attachment Status: deleted
--- Original message information follows ---
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Thu, 5
On Wed, Aug 04, 2004 at 10:34:34PM +0100, Jonathan McDowell wrote:
> I'm seeing the above error, with the following traceback, when my
> machine loads the uss720 driver (for a Belkin F5U002).
>
> usb 1-2.4: new full speed USB device using address 3
> uss720: probe: vendor id 0x1293, device id 0x2
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[EMAIL PROTECTED]
This message has been rejected because it has
a potentially e
Hello altogether,
[Please cc me as I am not subscribed]
here are some interesting (not to say annoying) observations regarding
the usb->serial converter driver ftdi_sio. On vanilla kernels 2.6.7
and 2.6.8-rc3 I connected the device in question to the pc the first
time after reboot and got this:
#
Hi USB Gurus!
2.6.8-rc2-mm2
It just happened to me that my X stopped working (all frozen) while
syncing my palm. Sysrq/syslog brought forth:
vmunix: bad: scheduling while atomic!
vmunix: [] schedule+0x3d8/0x3e0
vmunix: [] usb_kill_urb+0xdd/0x160 [usbcore]
vmunix: [] autoremove_wake_function+0
26 matches
Mail list logo
