From: Michiel Ronsse <Michiel.Ronsse@rug.ac.be>
To: mtd@infradead.org
Subject: Re: SBC-MediaGX
Date: Fri, 29 Sep 2000 19:20:46 +0200 [thread overview]
Message-ID: <39D4CF6E.76E89B@rug.ac.be> (raw)
In-Reply-To: E13f1t2-0003Zd-00@pearl.tao.co.uk
David Given wrote:
>
> >after checking all the messages in the archive of this
> >mailing list I managed to access the Intel Strataflash
> >chip on our Arcom SBC-MediaGX board. I 'repartitioned' the flash:
> >256kB for the BIOS extension, 1.5MB for DOS and the remainder
> >for Linux. The linux partition was formatted with JFFS.
> >Everything seems to work find although JFFS makes a lot
> >of noise when mounting the partition, moreover it finds only
> >13MB free and df only reports 4MB free...
>
> There may be sectors needing garbage collection. Try syncing it and having
> another look. As for why it's so slow, I'm not sure, but someone posted a
> patch a few days ago that should speed things up considerably (I haven't tried
> it).
It seems the JFFS image made by mk.jffs was totaly f**ked up. The
garbage
collector freaked out after a while (endless loop) and managed to erase
the first few bytes from my FlashFX-BIOS image! However after each few
reboot/
mount/garbage collections everything seems to work fine now. Actually,
it
works like a charm!
> >The next logical step would be to make the flash bootable
> >by overwriting the BIOS extension. I'm a bit reluctant to
> >do this as I don't want to make my board unbootable. E.g.
> >what happens if there is something wrong with the new BIOS?
> >Can you prevent somehow the BIOS on the board
> >from executing the BIOS extension in the flash?
>
> My understanding (you better check this before trying anything) is that the
> BIOS extension only contains the VBF code needed for DOS to see the VBF
> volume. If you trash it, all that will happen is that you won't be able to
> access the VBF volume, and you can always reinstall it from the Arcom floppy.
> The BIOS itself is in another flash chip entirely. I think.
As I understand it, the BIOS is in the first 256kB of the flash.
Disassembling
the first few bytes surely look like the start of a BIOS extension (e.g.
it
starts with the magic numbers AA55). Actually, after the first bytes
were
wiped out by the garbage collector, I couldn't access the Flash-drive
under DOS
anymore (the FlashFX message that 'flashes' by at bootup didn't appear
=> no
BIOS extension installed.)
>
> What do you have in mind for a boot loader?
Good question that remains to be answered...
>
> >Another question: why is the BIOS extension area soo big as
> >the extension itself is only about 14kB? The autoexec.bat file
> >on the Arcom bootfloppy mentions that the extension was enlarged
> >some time ago to 256KB in order to accomodate the Windows CE
> >registry???
>
> Don't know. I stuck with 256kB on my board for the same reason you did. I
> don't think it's critical; what's the maximum size for a ROM extension? 16kB?
> 32kB?
The memory window it takes up at bootup (processor in real mode) is only
16kB big,
so this seems to be the maximum.
Michiel Ronsse.
BTW: my board now works like a charm. The flash starts with a BIOS
extension of
256kB, followed by a DOS/FlashFX partition of 1MB containing
loadlin+vmnlinuz and
I have a minimal Linux-system in the last partition of around 15MB.
--
+- Michiel Ronsse --- michiel.ronsse@rug.ac.be -+
| Parallel Information Systems Group |
| ELIS - Ghent University - Ghent, Belgium |
| Phone: +32/9/264.33.67 Fax: +32/9/264.35.94 |
+------ http://www.elis.rug.ac.be/~ronsse ------+
In a train station the train stops, in a work station ...
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-09-29 17:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-29 12:55 SBC-MediaGX Michiel Ronsse
2000-09-29 15:15 ` SBC-MediaGX David Given
2000-09-29 17:20 ` Michiel Ronsse [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-29 17:47 re[2]: SBC-MediaGX Tony Questad
2000-09-30 11:19 ` SBC-MediaGX Alex J Lennon
[not found] <NEBBLLDBMLGONJHPHHEKGEMLCHAA.ajlennon@arcom.co.uk>
2000-09-14 12:54 ` sbc-mediagx David Woodhouse
2000-09-14 13:12 ` sbc-mediagx Alex J Lennon
2000-09-14 13:20 ` sbc-mediagx David Woodhouse
2000-09-15 20:23 ` sbc-mediagx Scott Anderson
[not found] <39C08AB9.1DF0409B@arcom.co.uk>
2000-09-14 10:59 ` sbc-mediagx David Given
2000-09-14 11:45 ` sbc-mediagx Kira Brown
2000-09-13 16:27 sbc-mediagx David Given
2000-09-13 16:43 ` sbc-mediagx David Woodhouse
2000-09-13 17:08 ` sbc-mediagx David Given
2000-09-13 17:37 ` sbc-mediagx David Given
2000-09-13 18:10 ` sbc-mediagx David Given
2000-09-14 9:04 ` sbc-mediagx David Woodhouse
2000-09-14 10:03 ` sbc-mediagx David Given
2000-09-14 11:15 ` sbc-mediagx David Given
2000-09-14 9:35 ` sbc-mediagx David Vrabel
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=39D4CF6E.76E89B@rug.ac.be \
--to=michiel.ronsse@rug.ac.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.