From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-DM] List of offending drivers
Date: Tue, 31 Jul 2012 03:50:07 -0400 [thread overview]
Message-ID: <201207310350.09208.vapier@gentoo.org> (raw)
In-Reply-To: <20120727044145.8994C200347@gemini.denx.de>
On Friday 27 July 2012 00:41:45 Wolfgang Denk wrote:
> Marek Vasut wrote:
> > Check the following list, it's the list of drivers scattered (misplaced)
> > across the tree. The list is not complete and might be inaccurate. But
> > it should give a good impression of what I'm going to break soon:
> >
> > board/bf533-ezkit/flash.c
>
> 1) old versions of flash drivers that predate the cfi flash
> implementation, so they could be replaced by the CFI driver (if
> there was someone to test this)
yep. this driver is wicked old, and has since languished for a few reasons:
- the people who wrote it originally were (are) not exactly great
programmers. in fact, they were pretty terrible.
- this particular board is one of the first Blackfins to see a real open source
port, but the board itself isn't terribly developer friendly, so no one pays
too much attention to it.
- the flash does not support the CFI query command which means none of the
stock CFI code would work out of the box (it does use the AMD CFI commandset
though).
- the flash is funky -- it's two chips in a single package which leads to
quite a bit of confusion, and it also has SRAM areas on it !
- the Blackfin maintainers who took over weren't terribly familiar with the
CFI spec (i would say i only have a little familiarity at a higher level).
at any rate, i was able to figure out the JEDEC probe logic in Linux somewhat
recently to make it work there, and so i ported that to u-boot which means we
can drop this old driver (patches already posted). seems to
probe/read/erase/write just fine, so ship it ;).
> > board/bct-brettl2/gpio_cfi_flash.c
> > board/cm-bf527/gpio_cfi_flash.c
> > board/cm-bf537e/gpio_cfi_flash.c
> > board/cm-bf537u/gpio_cfi_flash.c
> > board/tcm-bf537/gpio_cfi_flash.c
>
> 2) very special versions of flash drivers dealing with board specific
> details that prevent the use of the CFI flash driver, in which case
> they should remain in the board directories.
yep. these are merely glue to support the flashes on these boards that use
GPIO's for additional address lines. they actually use the common CFI code
already.
there is a thread from a while ago discussing how to make these work better in
the larger u-boot framework (NOR flashes which are not fully directly mapped),
but i honestly don't think i'll ever get around to implementing that idea. i
have no job that requires it, and only had a passing interest in implementing
it ;).
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120731/6d6cff13/attachment.pgp>
next prev parent reply other threads:[~2012-07-31 7:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 23:18 [U-Boot] List of offending drivers Marek Vasut
2012-07-27 1:08 ` [U-Boot] [U-Boot-DM] " Graeme Russ
2012-07-27 1:11 ` Marek Vasut
2012-07-27 1:20 ` Graeme Russ
2012-07-27 1:26 ` Marek Vasut
2012-07-27 1:29 ` Graeme Russ
2012-07-27 1:37 ` Marek Vasut
2012-07-27 4:41 ` Wolfgang Denk
2012-07-27 8:42 ` Marek Vasut
2012-07-27 9:33 ` Wolfgang Denk
2012-07-31 7:50 ` Mike Frysinger [this message]
2012-07-27 6:28 ` [U-Boot] " Lukasz Majewski
2012-07-27 8:43 ` Marek Vasut
2012-07-27 14:11 ` Igor Grinberg
2012-07-27 14:30 ` Marek Vasut
2012-07-27 14:45 ` Igor Grinberg
2012-07-27 14:49 ` Marek Vasut
2012-08-01 10:11 ` [U-Boot] [U-Boot-DM] " Andreas Bießmann
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=201207310350.09208.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.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