From: Thomas Hood <jdthood@mail.com>
To: "Jörg Ziuber" <ziuber@ict.uni-karlsruhe.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PnP BIOS patch against 2.4.12-ac2
Date: 17 Oct 2001 09:41:07 -0400 [thread overview]
Message-ID: <1003326069.14282.171.camel@thanatos> (raw)
In-Reply-To: <3BCD2510.9633D2BD@ict.uni-karlsruhe.de>
In-Reply-To: <E15t6nz-000205-00@the-village.bc.nu> <1003202856.12542.57.camel@thanatos> <3BCBE89C.ADD98E21@ict.uni-karlsruhe.de> <1003268655.12542.67.camel@thanatos> <3BCD2510.9633D2BD@ict.uni-karlsruhe.de>
On Wed, 2001-10-17 at 02:28, Jörg Ziuber wrote:
> Thomas Hood wrote:
> > Is this problem related to the PnP BIOS patch? That is,
> > do you have the same problem with a kernel that lacks the
> > patch?
>
> Maybe it is related.
> This is at least a Sony Vaio problem, because attaching the same USB
> device to other PCs with the same (kernel)installation works without
> problems.
> It was checked to be USB-device-independent with the Vaio (same problem
> with any device).
> Because USB even works on the Vaio under Windows, the USB developers
> (uhci) told me to look in linux-kernel for the PCI/IRQ programmers due
> to a potentially broken BIOS ("IRQ routing problem")- that's where I am
> now (?).
>
> A kernel without the patch results in the same non-recognition
> (non-USB-number-assignment) of the USB device, but when booting I get
> errors concerning a multiple reservation of IRQ9. With the patch there
> are no errors of that kind (see last mail).
That puzzles me. I'm not sure how my patch could affect
IRQ handling. Could you please try the version of the
patch that I submitted last night under the title
"[PATCH] PnP BIOS -- new"? Let me know whether you do
or you do not get the error messages concerning multiple
reservations of IRQ9.
> And the "feature", that USB
> works when the shared interrupt is busy (same effect with unpatched
> kernel), makes me feel that there is a IRQ problem, specific to Sony
> Vaio. So, the PnP-BIOS-patch is my hope because it cares about Sony Vaio
> (BIOS/IRQ?) specials.
I wouldn't hope too strongly that my patch will help you.
Just to be clear. IIUC you are saying that my patch isn't
the cause of your problem; it's just that it doesn't solve
your problem. Is that right?
--
Thomas
next prev parent reply other threads:[~2001-10-17 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 15:40 [PATCH] PnP BIOS -- bugfix; update devlist on setpnp Thomas Hood
2001-10-15 6:37 ` Jurgen Botz
2001-10-15 9:45 ` Stelian Pop
2001-10-15 12:01 ` Andrey Panin
2001-10-15 12:25 ` Alan Cox
2001-10-15 21:49 ` Thomas Hood
2001-10-16 3:27 ` [PATCH] PnP BIOS patch against 2.4.12-ac2 Thomas Hood
2001-10-16 7:58 ` Jörg Ziuber
2001-10-16 21:44 ` Thomas Hood
2001-10-17 6:28 ` Jörg Ziuber
2001-10-17 13:41 ` Thomas Hood [this message]
2001-10-17 14:43 ` Jörg Ziuber
2001-10-17 20:43 ` Thomas Hood
2001-10-15 14:15 ` [PATCH] PnP BIOS -- bugfix; update devlist on setpnp Ion Badulescu
2001-10-17 2:48 ` Steven A. DuChene
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=1003326069.14282.171.camel@thanatos \
--to=jdthood@mail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ziuber@ict.uni-karlsruhe.de \
/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