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 1AE74F652ECB1440B73DD7C2C20842D1B3A663@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