From: Bukie Mabayoje <bukiemab@gte.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EBDA Question
Date: Sat, 26 Feb 2005 11:08:21 -0800 [thread overview]
Message-ID: <4220C925.59995262@gte.net> (raw)
In-Reply-To: cubhu5$3jf$1@terminus.zytor.com
"H. Peter Anvin" wrote:
> Followup to: <91888D455306F94EBD4D168954A9457C01297B87@nacos172.co.lsil.com>
> By author: "Moore, Eric Dean" <Eric.Moore@lsil.com>
> In newsgroup: linux.dev.kernel
> >
> > EBDA - Extended Bios Data Area
> >
> > Does Linux and various boot loaders(lilo/grub/etc)
> > having any restrictions on where and how big
> > memory allocated in EBDA is? Is this
> > handled for 2.4/2.6 Kernels?
> >
> > Reason I ask is we are considering having
> > BIOS(for a SCSI HBA Controller) allocating
> > memory in EBDA for Firmware use.
> > We are concerned whether Linux would be writing
> > over this region of memory during the handoff
> > of BIOS to scsi lower layer driver loading.
> >
>
> In general, dropping the EBDA below 0x9a000 is probably a
> bad idea. Recent Linux kernels and boot loaders should handle it,
> though. Keep in mind that you might find yourself in serious trouble
> if you then have, for example, a PXE stack layered on top of your SCSI
> BIOS.
There are test software used in manufacturing line that needs this DOS memory.
>
>
> -hpa
>
> -
> 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/
next prev parent reply other threads:[~2005-02-26 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 19:45 EBDA Question Moore, Eric Dean
2005-02-08 23:28 ` H. Peter Anvin
2005-02-26 19:08 ` Bukie Mabayoje [this message]
2005-02-27 3:42 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2005-02-07 20:54 Salyzyn, Mark
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=4220C925.59995262@gte.net \
--to=bukiemab@gte.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@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