From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Tomasz Sterna <smoku@jaszczur.org>
Cc: James Simmons <jsimmons@linux-fbdev.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: standard_io_resources[]
Date: Thu, 22 Mar 2001 05:38:32 -0500 [thread overview]
Message-ID: <3AB9D628.5B01E8B@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0103210908560.2648-100000@linux.local> <20010322094159.A7407@plwawtl0.pl.ccbeverages.com>
Tomasz Sterna wrote:
>
> On Wed, Mar 21, 2001 at 09:13:05AM -0800, James Simmons wrote:
> > >Isn't that a job of the device drivers?
> > Well most of those resources are present on every PC motherboard.
>
> I still can't see a reason for allocating it before the device drivers
> could do that.
>
> Any suggestions? Anyone?
If you write into those resources and they are absent, bad things
sometimes happen. So, they are always added to the reserved-resource
list. I already had this argument with Linus :)
Jeff
--
Jeff Garzik | May you have warm words on a cold evening,
Building 1024 | a full mooon on a dark night,
MandrakeSoft | and a smooth road all the way to your door.
next prev parent reply other threads:[~2001-03-22 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 17:13 James Simmons
2001-03-22 8:41 ` standard_io_resources[] Tomasz Sterna
2001-03-22 10:38 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-22 7:41 standard_io_resources[] James Simmons
2001-03-22 7:40 standard_io_resources[] James Simmons
2001-03-20 9:16 standard_io_resources[] Tomasz Sterna
2001-03-20 9:56 ` standard_io_resources[] Andrzej Krzysztofowicz
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=3AB9D628.5B01E8B@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=jsimmons@linux-fbdev.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smoku@jaszczur.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