Ampro again

Ampro again

[Nick Maximov]

I have got no response from anyone. 
Just one question -- how safe to deal with mtd drivers and firmware
updates (for grub) on Ampro hardware (CoreModule P5e-Q04).
One thing stops me -- Ampro has their own format and update
utilities which are incompatible with M-Systems' ones.
Does mtd utilities works on that modules? I affraid to crash BIOS again...
May I produce file to load it to extended area via supplied pformat 
utility? Is that better way?
And what the latest stable kernel works better with this drivers?

Thank you again...

Nick Maximov. 


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

Re: Ampro again

[David Woodhouse]

On Fri, 13 Oct 2000, Nick Maximov wrote:

> 
> I have got no response from anyone. 
> Just one question -- how safe to deal with mtd drivers and firmware
> updates (for grub) on Ampro hardware (CoreModule P5e-Q04).
> One thing stops me -- Ampro has their own format and update
> utilities which are incompatible with M-Systems' ones.

Ampro have their own software which is incompatible with the M-Systems
code but works on DiskOnChip?

> Does mtd utilities works on that modules? I affraid to crash BIOS again...
> May I produce file to load it to extended area via supplied pformat 
> utility? Is that better way?

Yes, and it shouldn't be too difficult. Look at the format of the .EXB
file and compare it with what you can read from the DiskOnChip using the
MTD driver. It should be fairly simple to produce utilities which do the
conversion to/from EXB and raw binary. (Famous last words, I know :)


> And what the latest stable kernel works better with this
drivers? 

Anything 2.2 or 2.4 should work, although if you use an older 2.2 you 
need to nick include/linux/compatmac.h from a newer one.

-- 
dwmw2




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

Re: Ampro again

[Nick Maximov]

David Woodhouse wrote:
> 
> On Fri, 13 Oct 2000, Nick Maximov wrote:
> 
> >
> > I have got no response from anyone.
> > Just one question -- how safe to deal with mtd drivers and firmware
> > updates (for grub) on Ampro hardware (CoreModule P5e-Q04).
> > One thing stops me -- Ampro has their own format and update
> > utilities which are incompatible with M-Systems' ones.
> 
> Ampro have their own software which is incompatible with the M-Systems
> code but works on DiskOnChip?

YES! Note about that! Ampro manual says: "Do not use M-Systems pformat
and
pupdate utilities. These utilities are incompatible. Use p5format and
p5update
instead." BUT: Using M-Systems binary linux driver for produce TrueFFS
support
under linux works OK, except booting from DoC. Patched version of lilo
does
not works properly. 

I am not sure if I have crashed my bios using M-Systems utilities, but
chance 
to crash BIOS still exists.

Are MTD drivers based originally on M-Systems implementation or you have
writen your own driver set? As I understand if M-System's code
potentially may
crash Ampro DoC2000 BIOS, such code should not be used???

DoC became unavailable is what happened in previous attempt to load new
firmware
as EXB file using doc_loadbios. :(

I do not understand the difference between NAND devices and other
devices. Which
class of device I have installed on my module?


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

Re: Ampro again

[David Woodhouse]

maxs@techno.spb.ru said:
>  Are MTD drivers based originally on M-Systems implementation or you
> have writen your own driver set?

Our code isn't based on M-Systems' implementation - it's written entirely 
from scratch according to the documentation.

> I do not understand the difference between NAND devices and other
> devices. Which class of device I have installed on my module? 

The DiskOnChip contains NAND flash devices. 


--
dwmw2




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