From: Nick Maximov <maxs@techno.spb.ru>
To: MTD <mtd@infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>
Subject: Re: Ampro again
Date: Mon, 16 Oct 2000 10:47:43 +0400 [thread overview]
Message-ID: <39EAA48F.1FAB34F5@techno.spb.ru> (raw)
In-Reply-To: Pine.LNX.4.21.0010151510010.20018-100000@imladris.demon.co.uk
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
next prev parent reply other threads:[~2000-10-16 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-13 18:08 Ampro again Nick Maximov
2000-10-15 14:24 ` David Woodhouse
2000-10-16 6:47 ` Nick Maximov [this message]
2000-10-16 8:05 ` 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=39EAA48F.1FAB34F5@techno.spb.ru \
--to=maxs@techno.spb.ru \
--cc=dwmw2@infradead.org \
--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