All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Williams <gfi8d1h02@sneakemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: A Shared flash.c
Date: Fri, 05 Mar 2004 15:06:22 -0800	[thread overview]
Message-ID: <6922-64489@sneakemail.com> (raw)
In-Reply-To: <20040305214248.6AC5BC0655@atlas.denx.de>

Wolfgang Denk wd-at-denx.de |u-boot-users| wrote:
> In message <26365-62604@sneakemail.com> you wrote:
> 
>>Well gee, it seems like flash_print_info in particular should
>>go into the cmd_flash.c file, *inside* the (CONFIG_COMMANDS & CFG_CMD_FLASH)
>>section. The flinfo command is the only place it is used. There
>>are a few other functions like that, but print_flash_info is the
>>most glaring example.
> 
> 
> Please have a look over the rim. There are other flash drivers  which
> are just different.

OK, that's true about the flash.c file as a whole, but the
print_flash_info functions are all board independent, as far
as I can see. Just different levels of completeness. There
are other similar functions that only peruse the flash_info
structures and so are completely board independent, and I
was merely thinking in terms of unifying some common code.

Again, I see your point WRT flash.c as a whole, but wouldn't
it be useful to for example make flash_print_info common?

Granted that's a lot of board files implementing the same
print_flash_info, so maybe surround a common version with
CFG_FLASH_COMMON_PRINT and use that for the few that are
staring me in the face.
-- 
Steve Williams                "The woods are lovely, dark and deep.
steve at XXXXXXXXXX           But I have promises to keep,
http://www.XXXXXXXXXX         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

  reply	other threads:[~2004-03-05 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4048BB13.6090103@icarus.com>
2004-03-05 17:54 ` [U-Boot-Users] Re: A Shared flash.c Stephen Williams
2004-03-05 21:42   ` Wolfgang Denk
2004-03-05 23:06     ` Stephen Williams [this message]
2004-03-05 23:19       ` Wolfgang Denk

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=6922-64489@sneakemail.com \
    --to=gfi8d1h02@sneakemail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.