Hello Sebastian,
On Fri, Nov 14, 2014 at 09:21:00AM +0100, Sebastian Hesselbarth wrote:
> On 11/13/2014 07:44 PM, Uwe Kleine-König wrote:
> >With a proper image I get barebox up now.
>
> Great, does that help with the ethernet issues you have been seeing
> before?
No, still having issues with eth
On 11/13/2014 07:44 PM, Uwe Kleine-König wrote:
On Thu, Nov 13, 2014 at 12:31:08PM +0100, Sebastian Hesselbarth wrote:
$ scripts/kwboot -b ../barebox-globalscale-mirabox.img -t /dev/ttyUSB1
Sending boot message. Please reboot the target...\
Sending boot image...
0 % [.
Hallo Sebastian,
On Thu, Nov 13, 2014 at 12:31:08PM +0100, Sebastian Hesselbarth wrote:
> >I don't manage to boot via UART. The usual outcome is:
> >
> >Sending boot message. Please reboot the target...\
> >Sending boot image...
> > 0 %
> > [.
On 11/13/2014 11:46 AM, Uwe Kleine-König wrote:
On Thu, Nov 13, 2014 at 10:53:46AM +0100, Sebastian Hesselbarth wrote:
On 11/13/2014 10:09 AM, Uwe Kleine-König wrote:
On Wed, Nov 12, 2014 at 12:22:22PM +0100, Sebastian Hesselbarth wrote:
On 11/12/2014 11:56 AM, Uwe Kleine-König wrote:
Hello a
On Thu, Nov 13, 2014 at 10:53:46AM +0100, Sebastian Hesselbarth wrote:
> On 11/13/2014 10:09 AM, Uwe Kleine-König wrote:
> >On Wed, Nov 12, 2014 at 12:22:22PM +0100, Sebastian Hesselbarth wrote:
> >>On 11/12/2014 11:56 AM, Uwe Kleine-König wrote:
> >>>Hello again,
> >>>
> >>>here come the recent in
On 11/13/2014 10:09 AM, Uwe Kleine-König wrote:
On Wed, Nov 12, 2014 at 12:22:22PM +0100, Sebastian Hesselbarth wrote:
On 11/12/2014 11:56 AM, Uwe Kleine-König wrote:
Hello again,
here come the recent insights.
[...]
It seems to be not possible to easily dump the register space in both
U-Bo
On Wed, Nov 12, 2014 at 12:22:22PM +0100, Sebastian Hesselbarth wrote:
> On 11/12/2014 11:56 AM, Uwe Kleine-König wrote:
> >Hello again,
> >
> >here come the recent insights.
> [...]
> >
> >It seems to be not possible to easily dump the register space in both
> >U-Boot and barebox for comparison. m
On 11/12/2014 11:56 AM, Uwe Kleine-König wrote:
Hello again,
here come the recent insights.
[...]
It seems to be not possible to easily dump the register space in both
U-Boot and barebox for comparison. md 0xf1074000+0x4000 just hangs
somewhere in the middle.
A difference between U-Boot and
Hello again,
here come the recent insights.
On Tue, Nov 11, 2014 at 10:06:49AM +0100, Uwe Kleine-König wrote:
> shouldn't it? It has the address 192.168.77.1). Running "ping 192.168.77.1"
> seems to result in packages like this:
>
> 10:01:30.233928 42:40:00:10:40:60 > 00:00:00:34:00:12, ethertyp
On Tue, Nov 11, 2014 at 11:34:30AM -0300, Ezequiel Garcia wrote:
> On 11/11/2014 11:31 AM, Thomas Petazzoni wrote:
> > Dear Ezequiel Garcia,
> >
> > On Tue, 11 Nov 2014 11:25:40 -0300, Ezequiel Garcia wrote:
> >
> >> Fix the produced kwbimage.cfg to boot from UART (actually, I think it's
> >>
Hi Ezequiel,
On Tue, Nov 11, 2014 at 11:25:40AM -0300, Ezequiel Garcia wrote:
> On 11/11/2014 06:06 AM, Uwe Kleine-König wrote:
> >>>
> >>> Do you have a command line for me? I used
> >>>
> >>> scripts/kwboot -b images/barebox-netgear-rn104-uart.img /dev/ttyUSB0
> >>>
> >>> which took much longe
On 11/11/2014 11:31 AM, Thomas Petazzoni wrote:
> Dear Ezequiel Garcia,
>
> On Tue, 11 Nov 2014 11:25:40 -0300, Ezequiel Garcia wrote:
>
>> Fix the produced kwbimage.cfg to boot from UART (actually, I think it's
>> not needed):
>>
>> diff --git a/arch/arm/boards/plathome-openblocks-ax3/kwbim
Dear Ezequiel Garcia,
On Tue, 11 Nov 2014 11:25:40 -0300, Ezequiel Garcia wrote:
> Fix the produced kwbimage.cfg to boot from UART (actually, I think it's not
> needed):
>
> diff --git a/arch/arm/boards/plathome-openblocks-ax3/kwbimage.cfg
> b/arch/arm/boards/plathome-openblocks-ax3/kwbima
Uwe,
On 11/11/2014 06:06 AM, Uwe Kleine-König wrote:
>>>
>>> Do you have a command line for me? I used
>>>
>>> scripts/kwboot -b images/barebox-netgear-rn104-uart.img /dev/ttyUSB0
>>>
>>> which took much longer than I expected (didn't time it, but I'd say in
>>> the several minutes range). And
Hello Sebastian,
On Mon, Nov 10, 2014 at 08:36:07PM +0100, Sebastian Hesselbarth wrote:
> On 11/10/2014 07:43 PM, Uwe Kleine-König wrote:
> >On Mon, Nov 10, 2014 at 03:10:56PM -0300, Ezequiel Garcia wrote:
> >>On 11/10/2014 05:06 AM, Uwe Kleine-König wrote:
> >>>I tested this series on top of 784b
On 11/10/2014 07:43 PM, Uwe Kleine-König wrote:
On Mon, Nov 10, 2014 at 03:10:56PM -0300, Ezequiel Garcia wrote:
On 11/10/2014 05:06 AM, Uwe Kleine-König wrote:
I tested this series on top of 784b352aeeed with a patch to support my
ReadyNAS 104 (by Netgear, Armada 370 system, currently only sec
Hello Ezequiel,
On Mon, Nov 10, 2014 at 03:10:56PM -0300, Ezequiel Garcia wrote:
> On 11/10/2014 05:06 AM, Uwe Kleine-König wrote:
> > I tested this series on top of 784b352aeeed with a patch to support my
> > ReadyNAS 104 (by Netgear, Armada 370 system, currently only second stage
> > booting fro
On 11/10/2014 05:06 AM, Uwe Kleine-König wrote:
> Hello Ezequiel,
>
> On Sun, Nov 09, 2014 at 11:56:14AM -0300, Ezequiel Garcia wrote:
>> Very delayed third round of the support for the network controller present
>> on Marvell Armada 370/XP SoC.
>>
>> The first patch enables the peripherals in a P
Hello Ezequiel,
On Sun, Nov 09, 2014 at 11:56:14AM -0300, Ezequiel Garcia wrote:
> Very delayed third round of the support for the network controller present
> on Marvell Armada 370/XP SoC.
>
> The first patch enables the peripherals in a PUP register, which is required
> on RGMII ports.
>
> The
Very delayed third round of the support for the network controller present
on Marvell Armada 370/XP SoC.
The first patch enables the peripherals in a PUP register, which is required
on RGMII ports.
The second and third patches add support for Marvell's 88E1543 and 88E1545 PHY
chips.
The fourth p
20 matches
Mail list logo
