From: David Woodhouse <dwmw2@infradead.org>
To: Stephen Brown <sbrown@stirling-dynamics.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: quick question
Date: Thu, 26 Jun 2003 13:34:35 +0100 [thread overview]
Message-ID: <1056630874.27553.124.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <005301c33bda$9e5621a0$11c8a8c0@stevejunior>
Weird -- what did you do different between your reply directly to me
(which had correct References: headers) and your reply to the list
(which didn't, hence got rejected)?
(... and then what did you do differently in your _second_ reply to the
list, which worked?)
Had you deleted the mail to which you're replying, or changed folders
and were no longer looking at the same folder, or something?
You're using Outlook and Exchange, right?
On Thu, 2003-06-26 at 13:01, Stephen Brown wrote:
> hi,
>
> its a DOC 2000 , onboard 8 MB, it resides on the p5e module, Ampro have
> specifically changed the hardware to suit their SBC, which includes a bios
> copy from eprom, they provide utility tools similar to the 'm-sys' ones,
> except are specifically designed for Ampro, if you use the 'm-sys' tools the
> SBC won't boot as 'im assuming' the bios cannot be copied from eprom as the
> first bios screen wont load, this creates a DOS partition as well as a bios
> area stored close to the boot sector.
>
> 1st problem is, compiling the kernel for the Ampro p5e module takes a good
> half day!!
Weird -- why? Are you building on the board itself and starting from
'make clean' each time?
You ought to be able to make just the MTD and DiskOnChip modules to
match the kernel you're running, and shouldn't even need to reboot to
test them.
> 2nd problem, the preparation for a standard 'm-sys DOC' is not the same as
> in the specific tools that are written for the p5e module.
Interesting. Do you know what _address_ you tell the p5e DFORMAT utility
to find the DiskOnChip at? Or what address it finds it at?
> I tried quite a few different kernel compiles ( include MTD - etc etc - also
> tried the ones default with kernel 2.4.4 and the latest ones from web ) to
> try and make the DOC compatible with the real-time linux kernel, recompiled
> with RTLinux pre-1, but couldnt get it to work, this takes up a lot of time!
Can you remember details? Did the hardware driver manage to detect the
DiskOnChip and report its presence? Was it only a problem with the
_contents_ of the DiskOnChip?
> I cannot recompile the kernel for Red Hat 7.2 and RTLinux to include ext3
> fs, so I have learned to live with it as ext2.
Why so?
--
dwmw2
next prev parent reply other threads:[~2003-06-26 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 11:00 quick question Stephen Brown
2003-06-26 11:06 ` David Woodhouse
2003-06-26 12:26 ` Stephen Brown
[not found] ` <005301c33bda$9e5621a0$11c8a8c0@stevejunior>
2003-06-26 12:34 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-19 12:36 Quick question Gareth Williams
2001-10-19 12:22 ` David Woodhouse
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=1056630874.27553.124.camel@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sbrown@stirling-dynamics.com \
/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