From: Vipin Malik <vipin.malik@daniel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: rob@sysgo.de, Alexander Melichenko <AlexanderM@lrpeople.com>,
mtd@infradead.org, mark.langsdorf@amd.com
Subject: Re: Elan SC520 - problem with MTD
Date: Tue, 17 Apr 2001 11:47:45 -0500 [thread overview]
Message-ID: <3ADC73B1.1960BC87@daniel.com> (raw)
In-Reply-To: 5360.987524764@redhat.com
David Woodhouse wrote:
> vipin.malik@daniel.com said:
> > Anywhy, why I bring this is up, there is a *nasty* surprise waiting
> > for folks that use the default address of 0x8400000 as programmed by
> > the BIOS shipped with the board.
>
> OK, so it's likely that the two drivers use different addresses just
> because they expect the board to have been set up differently? Is it
> possible to read the current values of these registers and ioremap()
> accordingly? Then we can make it a config option to reprogram them to a
> sane address.
Well, that's assuming that the same regs are used by the different boot
utilities to
decode the FLASH banks. There are 15 different regs to do this job. You
can use any 2!
I guess that it could be done, you run though all 15 and (looking at the
bits) first figure out which
reg is used for the FLASH CS, then which address it's decoding the flash
at.
Urgh!
In a proper system, the physmap.c file is *not* the place to setup
chipselect registers. Like I said,
what I did was a hack to work around some work done by a hardware
challenged software guy ;)
Maybe just the warning that this funny business is going on and some
sample code, normally commented out,
to "fix it"?
Then when one, does one's own init routine and boots straight from flash,
they would have init the FLASH CS registers
to the proper place anyway so one wouldn't need to do this stuff in this
file anyway.
Vipin
>
>
> --
> dwmw2
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-04-17 16:47 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 [this message]
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
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=3ADC73B1.1960BC87@daniel.com \
--to=vipin.malik@daniel.com \
--cc=AlexanderM@lrpeople.com \
--cc=dwmw2@infradead.org \
--cc=mark.langsdorf@amd.com \
--cc=mtd@infradead.org \
--cc=rob@sysgo.de \
/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