From: Vojtech Pavlik <vojtech@suse.cz>
To: Anthony Spinillo <tspinillo@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: INTEL 845G Chipset IDE Quandry
Date: Mon, 3 Jun 2002 11:22:31 +0200 [thread overview]
Message-ID: <20020603112231.B13204@ucw.cz> (raw)
In-Reply-To: <20020603010412.26640.qmail@linuxmail.org>
On Mon, Jun 03, 2002 at 09:04:12AM +0800, Anthony Spinillo wrote:
> I fired up 2519 as a test, same resource collision problem.
In that case, probably only a BIOS upgrade (if there is one available)
can help.
>
> Tony
>
> ----- Original Message -----
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Date: 03 Jun 2002 02:13:45 +0100
> To: Vojtech Pavlik <vojtech@suse.cz>
> Subject: Re: INTEL 845G Chipset IDE Quandry
>
>
> > On Sun, 2002-06-02 at 22:30, Vojtech Pavlik wrote:
> > > On Sun, Jun 02, 2002 at 09:36:35PM +0200, Martin Dalecki wrote:
> > > > Anthony Spinillo wrote:
> > > > > Back to my original problem, will there be a fix before 2010? ;)
> > > >
> > > > Well since you have already tyred yourself to poke at it.
> > > > Well please just go ahead and atd an entry to the table
> > > > at the end of piix.c which encompasses the device.
> > > > Do it by copying over the next familiar one and I would
> > > > be really geald if you could just test whatever this
> > > > worked. If yes well please send me just the patch and
> > > > I will include it.
> > >
> > > Note it works with 2.5 already. We have the device there.
> >
> > If you look at why it fails it fails not because it isnt in the table
> > but because the PCI device has not been allocated resources properly by
> > the BIOS
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
> >
>
> --
> Get your free email from www.linuxmail.org
>
>
> Powered by Outblaze
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-06-03 9:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 1:04 INTEL 845G Chipset IDE Quandry Anthony Spinillo
2002-06-03 9:22 ` Vojtech Pavlik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 23:35 Anthony Spinillo
2002-06-02 10:16 Anthony Spinillo
2002-06-02 19:36 ` Martin Dalecki
2002-06-02 21:30 ` Vojtech Pavlik
2002-06-03 1:13 ` Alan Cox
2002-06-03 8:43 ` Vojtech Pavlik
2002-06-03 11:49 ` Kjartan Maraas
2002-06-03 10:10 ` Andre Hedrick
2002-06-03 4:46 ` Martin Dalecki
2002-06-03 8:47 ` Vojtech Pavlik
2002-06-03 8:04 ` Martin Dalecki
2002-06-03 9:37 ` Vojtech Pavlik
2002-06-03 9:28 ` Martin Dalecki
2002-06-02 1:58 Bartlomiej Zolnierkiewicz
2002-06-02 6:01 ` Martin Dalecki
2002-06-03 8:59 ` Andre Hedrick
2002-06-01 21:43 Anthony Spinillo
2002-06-01 11:03 Anthony Spinillo
2002-06-01 12:40 ` Alan Cox
2002-06-01 20:13 ` Andre Hedrick
2002-06-01 19:53 ` Andre Hedrick
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=20020603112231.B13204@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tspinillo@linuxmail.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