Re: [U-Boot] [PATCH u-boot-arm/next 1/2] OMAP3: igep00x0: Add config option to choose flash storage memory
On 07/16/2012 12:43 AM, Enric Balletbò i Serra wrote:
[snip]
I would like to investigateif we can do this using runtime detection instead of a separate config option. Give me some days. The runtime detection can be done reading the sysboot configuration for example. I think it's possible, do you think would be possible ?
Until we have the device model and the ability to see at run-time if we have say NAND or OneNAND (or neither!) we can't because we have to build-time define where the environment will be found.
On Mon, Jul 16, 2012 at 7:58 PM, Tom Rini trini@ti.com wrote:
On 07/16/2012 12:43 AM, Enric Balletbò i Serra wrote:
[snip]
I would like to investigateif we can do this using runtime detection instead of a separate config option. Give me some days. The runtime detection can be done reading the sysboot configuration for example. I think it's possible, do you think would be possible ?
Until we have the device model and the ability to see at run-time if we have say NAND or OneNAND (or neither!) we can't because we have to build-time define where the environment will be found.
-- Tom
Hi Enric,
Runtime detection is possible reading the sysboot as you said (in fact this is how we do it in the kernel) but as Tom said I didn't find a common way to do this. I guess you can manually detect the NAND type and configure the GPMC registers on the board code but I didn't see other OMAP boards doing this. Instead I found other examples of boards using compile options to choose between memory types.
Of course I will be more than glad if you have a better approach to solve this :-)
Thanks a lot and best regards, Javier
On 07/16/2012 04:41 PM, Javier Martinez Canillas wrote:
[snip]
Runtime detection is possible reading the sysboot as you said (in fact this is how we do it in the kernel) but as Tom said I didn't find a common way to do this. I guess you can manually detect the NAND type and configure the GPMC registers on the board code but I didn't see other OMAP boards doing this. Instead I found other examples of boards using compile options to choose between memory types.
Of course I will be more than glad if you have a better approach to solve this :-)
The biggest problem is that today we don't have a way to read/write environment to a dynamically detected backing store. I had an idea on how to do this, but given the device model will also allow for this, easier, that's the way to go.
Hi,
2012/7/17 Tom Rini trini@ti.com:
On 07/16/2012 04:41 PM, Javier Martinez Canillas wrote:
[snip]
Runtime detection is possible reading the sysboot as you said (in fact this is how we do it in the kernel) but as Tom said I didn't find a common way to do this. I guess you can manually detect the NAND type and configure the GPMC registers on the board code but I didn't see other OMAP boards doing this. Instead I found other examples of boards using compile options to choose between memory types.
Of course I will be more than glad if you have a better approach to solve this :-)
The biggest problem is that today we don't have a way to read/write environment to a dynamically detected backing store. I had an idea on how to do this, but given the device model will also allow for this, easier, that's the way to go.
-- Tom
Cool, thanks for the explanations Tom.
Javier, of course you have my :-)
Acked-by: Enric Balletbo i Serra eballetbo@gmail.com
Cheers, Enric
participants (3)
-
Enric Balletbò i Serra -
Javier Martinez Canillas -
Tom Rini