Dear "Lv Terry-R65388",
Please stop top posting / full quoting.
This style of replying to messages ios a major PITA to deal with :-(
In message
<1ae74f652ecb1440b73dd7c2c20842d1b3a...@zch01exm27.fsl.freescale.net> you wrote:
>
> Though a block offset macros is more suitable for a block device,
> block size can be changed.
> Thus I think a size offset is better to describe the offset.
>
> What do you think?
I think you either did not read or understand what I wrote:
> Hm... I see a tendency to add more and more such files that all deal
> with one sort of a block oriented storage device or another. Should
> we not try to generalize this?
I was talking about a more generic support layer for block oriented
storage devices. In Unix, this is typically called a "block device",
but we probably don't have to go that far.
What are all these env_*.c files doing? Reading or writing one or
several blocks of data from a storage device and handing it over to
the environment code.
Maybe we can use a single generic file where each used driver
registers it's block read / block write functions?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
In the strict scientific sense we all feed on death -- even
vegetarians.
-- Spock, "Wolf in the Fold", stardate 3615.4
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
