FW: sbc-mediagx

Alex J Lennon ajlennon at arcom.co.uk
Thu Sep 14 08:43:27 EDT 2000


> Am I right in assuming that the partition sizes in sbc_mediagx.c are
> hard-coded and don't necessarily correspond to any particular
> region on the
> disk? FXINFO claims that the VBF partition starts at 256kB. Looking at
> dev/mtd/0, there's a ROM image in the bottom 8kB, and at 256kB there's
> something that looks suspiciously like a VBF header. I can
> certainly identify
> things like the volume serial number and various pieces of
> information that
> FXINFO gave me. These are then repeated every megabyte.
> ...

FlashFx implements VBF to support block access to the media and to provide
wear levelling amongst other things (I believe). The "Variable Block Flash"
is *not* a filesystem. It simply translates logical sector requests to
physical flash locations.

e.g. You might want to try to put together a FATxx filesystem on a FATxx
Linux would see the FAT structures when talking to the FlashFx driver but
the data
physically on the flash device would be FAT data blocks encapsulated within
the VBF

The VBF structures containing the FAT partition do start at 256Kb. The
(as supplied) utilises the bottom two erase zones for purposes other than
filesystem support.
NB. The JFFS implementation looks nothing like this.

> [...]
> >You won't beable to have both Linux and Dos booting of the flash.  Just
> >make sure you have a floppy drive to boot from...
> I have one, yes. However I'm extremely wary of playing with the
> flash; as far
> as I can determine, the FlashFX BIOS extension and, possibly, the
> Award BIOS
> itself are in the flash. If I erased it all from within Linux, I
> might nuke
> those as well and render the board unbootable. If anyone can
> comfirm that this
> is not the case, I would be most grateful.

Don't worry - the SBC-MediaGX BIOS is contained within a physically
flash device (for exactly the reasons you outline above). You cannot corrupt
the BIOS by experimenting with the resident flash array.

> Am I right in assuming that VBF is patented and closed? Is any
> information on
> it at all available, even just enough to identify the start of the VBF
> partition?

VBF is closed and proprietary as you suggest.

For the above reasons there is unlikely to be compatibility between a
FlashFx formatted
flash device (whatever filesystem you use) and MTD in the near future.

> >Arcom is currently in the process of producing a Linux dev. kit which
> >will do all this + booting for you.
> > Excellent.


	Alex Lennon, Arcom Control Systems ltd.

To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org

More information about the linux-mtd mailing list