From: "Gregory Schallert" <gschallert@dawning.com>
To: <mtd@infradead.org>
Subject: ELANSC400
Date: Fri, 21 Jul 2000 11:59:54 -0400 [thread overview]
Message-ID: <005001bff32c$b59a92a0$8e00a8c0@gpc> (raw)
In-Reply-To: Pine.LNX.4.21.0007211646360.22633-100000@alpha1.cygnus.co.uk
Well, Here's a new guy to the crowd.
I've Just started playing with the MTD drivers for linux and I have a couple
of questions.
I am currently working on a project that (will) store the linux kernel/os on
flash. We are useing the ElanSC400 chip and a board that has 3 pairs of
AM29F016EC Flash Chips arranged such that the high byte of the data goes to
one chip and the low byte goes to the other. I was wondering if the MTD
supports this? These chips are JEDEC compatiable.
Also I wrote a test program that run in user space and I tried using mmap()
to read the device and it seems to work OK as long as I map /dev/mem as
MAP_PRIVATE. I would like to be able to write to Memory < 1M directly. If
I change the flage to MAP_SHARED, mmap() falied with "Permision denied" Any
ideas?
Greg Schallert
Dawning Technoligies Inc
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-07-21 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 21:29 Jedec.c problems in mtd-20000704 mark.langsdorf
2000-07-21 15:53 ` David Woodhouse
2000-07-21 15:59 ` Gregory Schallert [this message]
2000-07-24 23:47 ` ELANSC400 Stuart Lynne
2000-07-25 8:59 ` ELANSC400 Kira Brown
2000-07-25 9:17 ` ELANSC400 Stuart Lynne
2000-07-25 9:31 ` ELANSC400 David Woodhouse
2000-07-26 18:29 ` Jedec.c problems in mtd-20000704 Jason Gunthorpe
2000-07-26 18:28 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2000-07-24 7:36 ELANSC400 Simon Munton
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='005001bff32c$b59a92a0$8e00a8c0@gpc' \
--to=gschallert@dawning.com \
--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