From: Robert Kaiser <rob@sysgo.de>
To: Vipin Malik <vipin.malik@daniel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Alexander Melichenko <AlexanderM@lrpeople.com>,
mtd@infradead.org
Subject: Re: Elan SC520 - problem with MTD
Date: Wed, 18 Apr 2001 15:14:56 +0200 [thread overview]
Message-ID: <01041815411600.00407@rob> (raw)
In-Reply-To: <3ADC62AE.66B350ED@daniel.com>
Hi Vipin,
On Die, 17 Apr 2001 you wrote:
>
> This is the board that I am working with myself. I've got this working for
> quite a while and have sent
> my "physmap.c" file to a few folks personally (that's the original physmap.c
> file from CVS hacked for the SC520 CDP- this was before there was
> a physmap file in CVS for this board.)
>
> [snip]
>
> I suggest that whoever checked the sc520cdp.c file into CVS,
.. That would be me ...
>,at the very least
> pick up the above comments
> and include them as a warning, even if they don't want to reprogram the PAR at
> the new and proper address
Sorry, I wasn't aware of your work in this area when I wrote sc520cdp.c and
decided to contribute it. My main goal was to use the flash for a JFFS
filesystem, so this strange mapping used by the BIOS wasn't a problem for me.
> (I suggest that we reprogram the PAR regs).
I tend to agree, though the fact that we are deviating from the BIOS's
configuration this way makes me wonder if there should be a config option
for it. OTOH, MTD already has more than enough config options already
and I'm hesitant to add another one. (Just try to imagine how to write a
one-paragraph entry for Configure.help to explain to people what this option
does without scaring them away).
Rob
----------------------------------------------------------------
Robert Kaiser email: rkaiser@sysgo.de
SYSGO RTS GmbH
Am Pfaffenstein 14 phone: (49) 6136 9948-762
D-55270 Klein-Winternheim / Germany fax: (49) 6136 9948-10
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-04-18 13:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 6:12 Elan SC520 - problem with MTD Alexander Melichenko
2001-04-11 12:22 ` Robert Kaiser
2001-04-11 14:33 ` Vipin Malik
2001-04-12 5:23 ` Alexander Melichenko
2001-04-17 13:38 ` David Woodhouse
2001-04-17 13:42 ` Robert Kaiser
2001-04-17 13:54 ` David Woodhouse
2001-04-17 13:58 ` Robert Kaiser
2001-04-17 14:08 ` David Woodhouse
2001-04-17 15:35 ` Vipin Malik
2001-04-17 16:26 ` David Woodhouse
2001-04-17 16:47 ` Vipin Malik
2001-04-17 22:16 ` David Woodhouse
2001-04-19 18:11 ` Robert Kaiser
2001-04-18 13:50 ` Robert Kaiser
2001-04-18 13:14 ` Robert Kaiser [this message]
2001-04-18 16:05 ` Vipin Malik
[not found] <Pine.LNX.4.21.0104151822270.6721-100000@dagobert.svc.sysgo.de>
2001-04-16 8:35 ` Alexander Melichenko
[not found] <Pine.LNX.4.21.0104161208120.12472-100000@dagobert.svc.sysgo.de>
[not found] ` <01041713245700.01481@rob>
[not found] ` <005801c0cbd3$2bdb3c60$4d02010a@lrpeople.com>
2001-04-23 9:59 ` Robert Kaiser
2001-04-23 13:10 ` David Woodhouse
2001-04-23 13:45 ` Alex Lennon
2001-04-23 13:54 ` Robert Kaiser
2001-04-23 14:26 ` Alex Lennon
2001-04-23 14:43 ` Robert Kaiser
2001-04-23 23:07 ` Vipin Malik
2001-04-24 7:56 ` Robert Kaiser
2001-04-24 12:28 ` David Woodhouse
2001-04-24 14:07 ` Ronald G Minnich
-- strict thread matches above, loose matches on Subject: below --
2001-04-26 18:23 mark.langsdorf
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=01041815411600.00407@rob \
--to=rob@sysgo.de \
--cc=AlexanderM@lrpeople.com \
--cc=dwmw2@infradead.org \
--cc=mtd@infradead.org \
--cc=vipin.malik@daniel.com \
/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