From: Alice Hennessy <ahennessy@mvista.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: ahennessy@mvista.com, mtd@infradead.org
Subject: Re: MTD support for 8x16 devices
Date: Thu, 31 Aug 2000 18:05:10 -0700 [thread overview]
Message-ID: <39AF00C6.DA335C86@mvista.com> (raw)
In-Reply-To: 9503.967625312@cygnus.co.uk
David Woodhouse wrote:
> ahennessy@mvista.com said:
> > Has any of this already been checked in recently? And what is the
> > procedure?
>
> Stéphane already pointed you at the latest CVS. If you want write access,
> let me have a SSH public key and a sample of your work :)
Ok, I will do that. I also just found out that I need to subscribe to the
mtd-cvs list to follow what is being checked in?
>
>
> Can you confirm the mapping of the flash chips - you've got two interleaved
> 16-bit devices ('2_by_16') but you can only actually access them a byte at
> a time? What is the CPU? What happens if you _do_ try to read a whole word
> instead of only a byte?
One product has two interleaved 16 devices and is recognized as such by
cfi_probe_new_chip() and can be read as a whole word.
The other product has a single strata chip (8x16 variety) set in byte mode so
the bus width is 1. The cfi ident info is requested at address 0xaa and read
starting at 0x20 so this is new code that I've added. I'll merge my code to
make use of the new define CFI_DEVICETYPE_X8 which I'm assuming was added for
this purpose?
The CPU is PPC405GP.
>
>
> ahennessy@mvista.com said:
> > I'm also thinking about different ways for the partition sizes to be
> > set outside of physmap.c. - any opinions? Perhaps board specifics
> > should be contained in a header file and be set via menuconfig or
> > command line or ?
>
> I think it's probably best to keep it in a header file or in physmap.c
> itself. The driver can default to no partitioning, and we can set up some
> #defines at the beginning which allow people to change it as they see fit.
Ok.
>
>
> ahennessy@mvista.com said:
> > 4. I need to implement a char device where the customer wants to
> > write to the flash and have all the erase details handle by the
> > driver. They want to simply do a dd into the device.
>
> No. Erase is a single ioctl() call, or a single invocation of the
> 'eraseall' utility. The customer is wrong. :)
Sooo, I need to do the extra logic outside the driver level. ;)
> --
> dwmw2
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
Thanks,
Alice
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-09-01 1:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-07 19:48 get_module_symbol / put_module_symbol Sébastien Côté
2000-08-08 7:47 ` David Woodhouse
2000-08-08 12:50 ` Sébastien Côté
2000-08-29 23:54 ` MTD support for 8x16 devices Alice Hennessy
2000-08-30 1:02 ` Stéphane Laroche
2000-08-30 8:48 ` David Woodhouse
2000-09-01 1:05 ` Alice Hennessy [this message]
2000-09-04 13:16 ` David Woodhouse
2000-09-07 18:39 ` get_module_symbol Alice Hennessy
2000-09-08 7:34 ` get_module_symbol 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=39AF00C6.DA335C86@mvista.com \
--to=ahennessy@mvista.com \
--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