From: Ian Thompson <ithompson@coollogic.com>
To: "mtd@infradead.org" <mtd@infradead.org>
Subject: lilo patch
Date: Wed, 13 Sep 2000 13:52:24 -0500 [thread overview]
Message-ID: <39BFCCE8.F95BA237@coollogic.com> (raw)
Forgive me if I'm covering familiar territory.
What was the purpose of the lilo-ebda.patch?
I have a development setup with a hard-drive and a DiskOnChip
and I was looking for a lilo patch that would allow me to boot
the hard-drive with a configured DiskOnChip in place but this
didn't do it.
I have a 32M DOC2000 @ 0xd000:0000
Other things I have noticed, that I, with my limited DOC knowledge,
can't explain...
A configured 32M Millenium will allow lilo to boot the hard-drive but
a configured 16M Millenium wiil not.
64M DOC2000s don't seem to work with M-Systems binary driver.
Has anyone any experience with 64M DOC2000s? We have several and
approx. 25% won't format to full capacity with the M-Systems utilities.
Ian T.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-09-13 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 18:52 Ian Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-14 16:41 lilo patch Miguel Freitas
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=39BFCCE8.F95BA237@coollogic.com \
--to=ithompson@coollogic.com \
--cc=mtd@infradead.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