public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: drivers/usb/core/config.c: invalid configuration descriptor
Date: Fri, 14 Nov 2003 15:53:07 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106882521025576@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106865176701709@msgid-missing>

David Mosberger <davidm@napali.hpl.hp.com> writes:

>>>>>> On Fri, 14 Nov 2003 14:03:04 +0100, Andreas Schwab <schwab@suse.de> said:
>
>   Andreas> Andreas Schwab <schwab@suse.de> writes:
>   >> When I try to run 2.6.0-test9 on an HP Everest I can't get USB
>   >> working.  All I get is this:
>
>   >> drivers/usb/core/usb.c: registered new driver hub PCI: Found IRQ
>   >> 52 for device 0000:01:04.0 IOSAPIC: vector 52 -> CPU 0x0200,
>   >> enabled ohci_hcd 0000:01:04.0: OHCI Host Controller ohci_hcd
>   >> 0000:01:04.0: irq 52, pci mem c000000088032000 ohci_hcd
>   >> 0000:01:04.0: new USB bus registered, assigned bus number 1
>   >> drivers/usb/core/config.c: invalid configuration descriptor
>
>   Andreas> This is actually a compiler bug, usb_parse_configuration
>   Andreas> gets miscompiled.
>
> Interesting.  Which compiler?

Nothing of interest, only some broken local changes.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

      parent reply	other threads:[~2003-11-14 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 15:37 drivers/usb/core/config.c: invalid configuration descriptor Andreas Schwab
2003-11-14 13:03 ` Andreas Schwab
2003-11-14 15:32 ` Randy.Dunlap
2003-11-14 15:46 ` David Mosberger
2003-11-14 15:53 ` Andreas Schwab [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-106882521025576@msgid-missing \
    --to=schwab@suse.de \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox