On Sat, Dec 08, 2012 at 11:54:13AM -0800, Simon Glass wrote:
> Hi Fabio,
>
> On Wed, Dec 5, 2012 at 5:30 PM, Fabio Estevam wrote:
> > On Wed, Dec 5, 2012 at 11:25 PM, Vadim Bendebury
> > wrote:
> >
> >> No - md/mw access memory, the new commands access the IO space (which
> >> is an x86 archite
Hi Fabio,
On Wed, Dec 5, 2012 at 5:30 PM, Fabio Estevam wrote:
> On Wed, Dec 5, 2012 at 11:25 PM, Vadim Bendebury wrote:
>
>> No - md/mw access memory, the new commands access the IO space (which
>> is an x86 architecture property).
>
> Ok, understood. On ARM we are able to access registers via
On Wed, Dec 5, 2012 at 11:25 PM, Vadim Bendebury wrote:
> No - md/mw access memory, the new commands access the IO space (which
> is an x86 architecture property).
Ok, understood. On ARM we are able to access registers via md/mw.
Maybe it would be better to put a note in the commit message that
On Wed, Dec 5, 2012 at 5:23 PM, Fabio Estevam wrote:
> On Wed, Dec 5, 2012 at 10:46 PM, Simon Glass wrote:
>> From: Vadim Bendebury
>>
>> Provide u-boot console functions to access IO space registers. A no
>> thrills implementation, accessing one register at a time.
>>
>> For example:
>> boo
On Wed, Dec 5, 2012 at 10:46 PM, Simon Glass wrote:
> From: Vadim Bendebury
>
> Provide u-boot console functions to access IO space registers. A no
> thrills implementation, accessing one register at a time.
>
> For example:
> boot > iod 80
> 0080: 0094
> boot > iod.w 80
> 008
From: Vadim Bendebury
Provide u-boot console functions to access IO space registers. A no
thrills implementation, accessing one register at a time.
For example:
boot > iod 80
0080: 0094
boot > iod.w 80
0080: 0094
boot > iod.b 80
0080: 94
boot > iow.b 0x80 12
b
6 matches
Mail list logo