On Fri, 2006-06-23 at 19:02 -0700, Greg KH wrote:
> That's all you have done here. Just moved the init to open, but this
> didn't change the logic at all as:
>
> > pl2303_set_termios (port, &tmp_termios);
>
> You then still call pl2303_set_termios(). How did this fix anything?
It i
This is a note to let you know that I've just added the patch titled
Subject: usbfs: use the correct signal number for disconnection
to my gregkh-2.6 tree. Its filename is
usbfs-use-the-correct-signal-number-for-disconnection.patch
This tree can be found at
http://www.kernel.or
This is a note to let you know that I've just added the patch titled
Subject: USB hub: don't return status > 0 from resume
to my gregkh-2.6 tree. Its filename is
usb-hub-don-t-return-status-0-from-resume.patch
This tree can be found at
http://www.kernel.org/pub/linux/kernel/peo
On Fri, Jun 23, 2006 at 11:12:35PM +0200, Guennadi Liakhovetski wrote:
> > As for the initial console rate mismatch on pl2303:
> >
> > pl2303_set_termios requires a private initialization flag
> > to be set (priv->termios_initialized) or it will
> > default to 9600 N81 instead of using the termios
On Friday 23 June 2006 3:55 am, Ralf Baechle wrote:
>
> First part looks a bit hackish... but it works for me.
I take it there's no cpu_is_au1500() macro to use? Maybe you should
add one, and start using it here.
Otherwise, the main reasons its hackish is that "not 1200" is not the
same as "is
On Sat, Jun 24, 2006 at 12:33:10AM +0200, Lennert Buytenhek wrote:
> On Fri, Jun 23, 2006 at 02:30:55PM -0700, David Brownell wrote:
>
> > > OK, it took a while, but here's a new patch for ep93xx ohci support,
> > > against 2.6.17-git5, with all previous feedback incorporated. It
> > > depends on
On Fri, Jun 23, 2006 at 02:30:55PM -0700, David Brownell wrote:
> > OK, it took a while, but here's a new patch for ep93xx ohci support,
> > against 2.6.17-git5, with all previous feedback incorporated. It
> > depends on the ep93xx implementation of the clk_* API, which is not
> > upstream yet an
Guennadi Liakhovetski wrote:
> The patch we are talking about is not pretty, and I am not sure it is
> correct. But if you think it is I would appreciate your "Acked-by" under
> it:-)
The module locking may not be a big deal (if the driver
is used as a console then it is in kernel anyways?), but
On Friday 23 June 2006 2:02 pm, Lennert Buytenhek wrote:
> OK, it took a while, but here's a new patch for ep93xx ohci support,
> against 2.6.17-git5, with all previous feedback incorporated. It
> depends on the ep93xx implementation of the clk_* API, which is not
> upstream yet and still sitting
On Friday 23 June 2006 1:36 pm, Ralf Baechle wrote:
> From: Daniel Mack <[EMAIL PROTECTED]>
>
> I received an DBAU1200 eval kit from AMD a few days ago and tried to
> enable the USB2 port, but the current linux-2.6 GIT did not even
> compile with CONFIG_SOC_1200, CONFIG_SOC_AU1X00, CONFIG_USB_EHCI
On Fri, 23 Jun 2006, Paul Fulghum wrote:
> Your patch is necessary to be correct because
> it locks the module on the first normal open.
> (even if pl2303 can run without it)
>
> I believe the original problem was that the lines
>
>tty->driver_data = port;
>port->tty = tty;
>
> were ori
On Fri, Mar 03, 2006 at 02:28:28AM +0100, Lennert Buytenhek wrote:
> > > + .start = ohci_ep93xx_start,
> > > + .stop = ohci_stop,
> > > + .urb_enqueue= ohci_urb_enqueue,
> > > + .urb_dequeue= ohci_urb_dequeue,
> > > + .endpoint_disable
From: Daniel Mack <[EMAIL PROTECTED]>
I received an DBAU1200 eval kit from AMD a few days ago and tried to
enable the USB2 port, but the current linux-2.6 GIT did not even
compile with CONFIG_SOC_1200, CONFIG_SOC_AU1X00, CONFIG_USB_EHCI and
CONFIG_USB_OHCI set.
Furthermore, in ehci-hcd.c, platform
On Fri, 23 Jun 2006, Luiz Fernando N. Capitulino wrote:
> Actually, I'm afraid the switch will not happen anymore [1]. :(
Well, there's a problem, but there should be a solution too, so, I don't
think it's a final verdict yet. I think, it's just a matter of finding a
proper solution to it.
>
> On Thu, 22 Jun 2006 22:50:23 +0200 (CEST)
> Guennadi Liakhovetski <[EMAIL PROTECTED]> wrote:
>
> | On Tue, 9 May 2006, Guennadi Liakhovetski wrote:
> |
> | > On Mon, 8 May 2006, Guennadi Liakhovetski wrote:
> | >
> | > > Yes. I put a WARN_ON(1) next to ++open_count in both files and I still
>
On Thu, 22 Jun 2006 09:29:40 +0100
Russell King <[EMAIL PROTECTED]> wrote:
| On Wed, Jun 21, 2006 at 06:15:13PM -0300, Luiz Fernando N. Capitulino wrote:
|
| > | With get_mctrl(), the situation is slightly more complicated, because
| > | we need to atomically update tty->hw_stopped in some circums
Hi Guennadi,
On Thu, 22 Jun 2006 22:50:23 +0200 (CEST)
Guennadi Liakhovetski <[EMAIL PROTECTED]> wrote:
| On Tue, 9 May 2006, Guennadi Liakhovetski wrote:
|
| > On Mon, 8 May 2006, Guennadi Liakhovetski wrote:
| >
| > > Yes. I put a WARN_ON(1) next to ++open_count in both files and I still
s
On Friday 23 June 2006 7:51 am, Alan Stern wrote:
> Ah, there's the rub. If a driver doesn't have suspend/resume methods, is
> it because it doesn't need them, or is it because nobody has written them
> yet? In the latter case, failing the suspend or unbinding the driver are
> the only safe c
On Thu, 22 Jun 2006, Greg KH wrote:
> > Under what scenario could it possibly be legitimate to suspend a
> > usb device -- or interface, or anything else -- with its children
> > remaining active? The ability to guarantee that could _never_ happen
> > was one of the fundamental motivations for th
On Thu, 22 Jun 2006, Greg KH wrote:
> > In my upcoming patch set this test isn't needed at all, because suspending
> > a device automatically suspends all of its interfaces first. I've already
> > submitted the first few revised patches in that set (not the part that
> > removes the test, though)
Hi all,
I have been dealing with the same error -110 for some time. Eventually i
found out that the clock divider suppling the clock to the USB host
controller (external Philips isp1161a) was not set up properly and hence
the timeouts. I don't know how it works with an onboard usb controller
b
WORM_NETSKY.DAM has been detected,and Replace has been taken on 6/23/2006
5:27:01 AM.
** Legal Disclaimer
"This email may contain confidential and privileged material for the sole use
of the intended recipient. Any unauthorized review, use or
当今网络营销最大的特点在于以消费者为导向。消费者将拥有比以往更大的
选择自由，他们可根据自己的个性特点和需求在全球范围内寻找满足自己需要的
产品和服务，不受地域限制。通过进入感兴趣的的网址或虚拟商店，消费者可获
取更多、尽显个性的空间和各种自由的服务空间。网络世界变幻莫测，游走在各
大网站这间的你是否已经寻求到属于自己的一片天空。这样就需要您擦亮您的眼
睛去审视一个网站的发展前景和它的发展力度。
http://wjjd.900me.com/go/gudong.asp
900Me是一个全新模式的专业上网导航，推广、应用、分红多种方式获取现
金收入。900Me将一直奉行
From: Domen Puncer <[EMAIL PROTECTED]>
Compile fixes for au1200 ohci.
First part looks a bit hackish... but it works for me.
Signed-off-by: Domen Puncer <[EMAIL PROTECTED]>
Index: linux-mailed/drivers/usb/host/ohci-au1xxx.c
===
On Fri, 23 Jun 2006 02:50:15 +0100 Sergio Monteiro Basto wrote:
> On Thu, 2006-06-22 at 18:39 -0700, Randy.Dunlap wrote:
> > This sounds like just running with CONFIG_IO_APIC=n or using
> > "noapic" on the kernel boot command line. If that's what is
> > needed, we can know that. I just haven't s
On Thu, 2006-06-22 at 18:39 -0700, Randy.Dunlap wrote:
> This sounds like just running with CONFIG_IO_APIC=n or using
> "noapic" on the kernel boot command line. If that's what is
> needed, we can know that. I just haven't seen info to know
> what the real problem is.
yes, could be a way, if we
Chris,
If you keep me posted on the patch when released (I'm not on the kernel
list, too high volume for me) I'll be happy to give your patch a whirl
on my test box against whichever kernel you patch.
Your last point is real good, how DOES Windows figure it out? In saying
that, without the VIA
On Fri, 23 Jun 2006 02:00:44 +0100 Sergio Monteiro Basto wrote:
> On Thu, 2006-06-22 at 15:54 -0700, Chris Wedgwood wrote:
> > On Thu, Jun 22, 2006 at 11:46:38PM +0100, Sergio Monteiro Basto wrote:
> >
> > > yap, in my opinion this function should back to
> >
> > > +DECLARE_PCI_FIXUP_ENABLE(PCI_
On Thu, 2006-06-22 at 16:25 -0700, Randy.Dunlap wrote:
> No idea about that.
> I think that you still didn't answer my question, or maybe I
> didn't ask it well enough. What device are you having problems
> with? I don't mean what chipset, I mean what device that you
> touch...
>
I'd like to giv
On Thu, 2006-06-22 at 15:54 -0700, Chris Wedgwood wrote:
> On Thu, Jun 22, 2006 at 11:46:38PM +0100, Sergio Monteiro Basto wrote:
>
> > yap, in my opinion this function should back to
>
> > +DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq);
>
>
> this is *obviousyl* wrong,
On Thu, 22 Jun 2006 23:46:38 +0100 Sergio Monteiro Basto wrote:
> On Thu, 2006-06-22 at 14:29 -0700, Randy.Dunlap wrote:
> > On Thu, 22 Jun 2006 12:56:25 +0100 Sergio Monteiro Basto wrote:
> >
> > > On Wed, 2006-06-21 at 21:08 -0700, Randy.Dunlap wrote:
> > > >
> > > > If you have a specific iss
On Thu, 2006-06-22 at 14:29 -0700, Randy.Dunlap wrote:
> On Thu, 22 Jun 2006 12:56:25 +0100 Sergio Monteiro Basto wrote:
>
> > On Wed, 2006-06-21 at 21:08 -0700, Randy.Dunlap wrote:
> > >
> > > If you have a specific issue/problem, it would probably be
> > > better just to focus on that.
> >
>
On Thu, 22 Jun 2006 12:56:25 +0100 Sergio Monteiro Basto wrote:
> On Wed, 2006-06-21 at 21:08 -0700, Randy.Dunlap wrote:
> >
> > If you have a specific issue/problem, it would probably be
> > better just to focus on that.
>
> on linux-2.6.17/drivers/pci/quirks.c
>
> * we must mask the PCI_
On Wed, 2006-06-21 at 21:08 -0700, Randy.Dunlap wrote:
>
> If you have a specific issue/problem, it would probably be
> better just to focus on that.
on linux-2.6.17/drivers/pci/quirks.c
* we must mask the PCI_INTERRUPT_LINE value versus 0xf to get
* interrupts delivered properly.
*/
On Thu, 22 Jun 2006 02:04:48 +0100 Sergio Monteiro Basto wrote:
> who no, how sorry! I am a little tired
>
> On Wed, 2006-06-21 at 17:47 -0700, Randy.Dunlap wrote:
> > On Thu, 22 Jun 2006 01:36:46 +0100 Sergio Monteiro Basto wrote:
> >
> > > who I do know if a interrupt is ioapic_edge_type or
who no, how sorry! I am a little tired
On Wed, 2006-06-21 at 17:47 -0700, Randy.Dunlap wrote:
> On Thu, 22 Jun 2006 01:36:46 +0100 Sergio Monteiro Basto wrote:
>
> > who I do know if a interrupt is ioapic_edge_type or ioapic_edge_type ?
>
> Do you mean how they are configured in a running ker
On Thu, 22 Jun 2006 01:36:46 +0100 Sergio Monteiro Basto wrote:
> who I do know if a interrupt is ioapic_edge_type or ioapic_edge_type ?
Do you mean how they are configured in a running kernel?
cat /proc/interrupts ::
CPU0 CPU1
0: 12412944 12407808IO-APIC-edge
Greg KH napsal(a):
> Mattai and Jiri, can you try the patch below to see if it fixes the USB
> suspend problem you are seeing with 2.6.17-mm1?
>
> David, we really should not be caring about what the children of a USB
> device is doing here, as who knows what type of "device" might hang off
> of a
On Thu, Jun 22, 2006 at 11:46:38PM +0100, Sergio Monteiro Basto wrote:
> yap, in my opinion this function should back to
> +DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq);
this is *obviousyl* wrong, it should never have been merged like that
and there are reports and com
On Fri, Jun 23, 2006 at 11:34:47AM +0530, Juhee MALA wrote:
> I am trying to configure a USB printer HP 3940 on my ARM based
> platform. TO do that I have downloaded the HP printer driver
> HPlip-0.9.11. But to compile it and to tun it on my platform, I am
> facing lot of problems. Has anybody done
Hi,
this adds
better debugging output &
an update of the quirk list
to the acm driver
Regards
Oliver
Signed-off-by: Oliver Neukum <[EMAIL PROTECTED]>
--- a/drivers/usb/class/cdc-acm.c 2006-06-23 07:25:44.0 +0200
+++ b/drivers/usb/class/cdc-acm.c 2006-
41 matches
Mail list logo
