From: Adam Agnew <agnew@missl.cs.umd.edu>
To: Mark Salter <msalter@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>, <waa@cs.umd.edu>,
<bdpayne@cs.umd.edu>, <usn01a@hotmail.com>
Subject: Re: [ECOS] RedBoot IDE access on x86 without BIOS
Date: Thu, 13 Sep 2001 06:53:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.33.0109130951120.60760-100000@www.missl.cs.umd.edu> (raw)
In-Reply-To: <200109131324.f8DDOY111277@deneb.localdomain>
On Thu, 13 Sep 2001, Mark Salter wrote:
> The IDE code in RedBoot assumes that the IDE controller/interface is
> initialized. If you aren't using the normal PC bios, perhaps the
> chipset has not been sufficiently initialized to support IDE.
Hrmm.. Interesting, yes, you're probably right! In fact, I found the patch
that makes Linux force the IDE controllers on in the LinuxBIOS -> kernel
configuration. I forgot about that and assumed RedBoot would just work
because the Linux kernel just worked. Alright, I'll get something in and
working real soon, and if there's a good generic way to do so on all x86s,
maybe it'd be worth it to fill in that HAL_IDE_INIT macro.
Thanks again, you probably just saved me days :)
- Adam
next prev parent reply other threads:[~2001-09-13 6:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 12:07 [ECOS] Problems with RedBoot on x86 generic pc Matthew M. DeLoera
2001-07-11 14:25 ` Jonathan Larmour
2001-07-31 7:59 ` Trenton D. Adams
2001-07-31 10:56 ` Jonathan Larmour
2001-07-31 12:01 ` Trenton D. Adams
2001-07-31 13:43 ` Jonathan Larmour
2001-07-31 14:20 ` Trenton D. Adams
2001-07-31 14:23 ` Jonathan Larmour
2001-09-07 11:25 ` Adam Agnew
2001-09-13 2:02 ` Adam Agnew
2001-09-13 3:56 ` [ECOS] RedBoot IDE access on x86 without BIOS Adam Agnew
2001-09-13 4:51 ` Mark Salter
2001-09-13 6:18 ` Adam Agnew
2001-09-13 6:24 ` Mark Salter
2001-09-13 6:53 ` Adam Agnew [this message]
2001-09-13 9:36 ` [ECOS] Problems with RedBoot on x86 generic pc Jonathan Larmour
2001-09-14 9:14 ` Adam Agnew
2001-09-14 12:43 ` Matthew DeLoera
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=Pine.BSF.4.33.0109130951120.60760-100000@www.missl.cs.umd.edu \
--to=agnew@missl.cs.umd.edu \
--cc=bdpayne@cs.umd.edu \
--cc=ecos-discuss@sources.redhat.com \
--cc=msalter@redhat.com \
--cc=usn01a@hotmail.com \
--cc=waa@cs.umd.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).