Peter Maydell a écrit :
On 23 December 2013 06:48, Hervé Poussineau wrote:
So, this patch is a small functional change, as it adds a copy of the
firmware in a new range 0xfff0-0xfff7, but I think we can live with
it.
We'll be able to remove it once we switch to another firmware which u
On 23 December 2013 06:48, Hervé Poussineau wrote:
> So, this patch is a small functional change, as it adds a copy of the
> firmware in a new range 0xfff0-0xfff7, but I think we can live with
> it.
>
> We'll be able to remove it once we switch to another firmware which uses the
> right re
Hi,
Andreas Färber a écrit :
Hi,
Am 05.11.2013 00:09, schrieb Hervé Poussineau:
Raven datasheet explains where firmware lives in system memory, so do
it there instead of in board code. Other boards using the same PCI
host will not have to copy the firmware loading code.
This part we had disc
Hi,
Andreas Färber a écrit :
Hi,
Am 05.11.2013 00:09, schrieb Hervé Poussineau:
Raven datasheet explains where firmware lives in system memory, so do
it there instead of in board code. Other boards using the same PCI
host will not have to copy the firmware loading code.
This part we had disc
Hi,
Am 05.11.2013 00:09, schrieb Hervé Poussineau:
> Raven datasheet explains where firmware lives in system memory, so do
> it there instead of in board code. Other boards using the same PCI
> host will not have to copy the firmware loading code.
This part we had discussed and no one objected to
Raven datasheet explains where firmware lives in system memory, so do
it there instead of in board code. Other boards using the same PCI
host will not have to copy the firmware loading code.
However, add a specific hack for Open Hack'Ware, which provides only
a 512KB blob to be loaded at 0xfff
