On Mon, Apr 11, 2022 at 2:11 PM Heinrich Schuchardt
wrote:
>
> A image_size parameter has been added to the bootefi parameter.
> Describe all parameters.
>
> Correct how the description of how the device-path in the loaded
> image protocol is determined.
>
> Signed-off-by: Heinrich Schuchardt
> -
On Mon, Apr 11, 2022 at 1:14 PM Heinrich Schuchardt wrote:
>
> On 4/10/22 23:05, kev...@freebsd.org wrote:
> > From: Kyle Evans
> >
> > Up until commit 5f59518a7b1ae ("efi_loader: setting boot device"), we
> > could boot an arbitrary blob with bootefi.
On Sat, Apr 9, 2022 at 5:37 AM Heinrich Schuchardt wrote:
>
> On 4/6/22 07:04, kev...@freebsd.org wrote:
> > From: Kyle Evans
> >
> > Up until commit 5f59518a7b1ae ("efi_loader: setting boot device"), we
> > could boot an arbitrary blob with bootefi.
On Mon, Apr 4, 2022 at 12:59 AM Heinrich Schuchardt wrote:
>
> Am 4. April 2022 07:40:16 MESZ schrieb Kyle Evans :
> >On Mon, Apr 4, 2022 at 12:09 AM Heinrich Schuchardt
> >wrote:
> >>
> >> Am 3. April 2022 23:08:33 MESZ schrieb Kyle Evans :
> >&g
On Mon, Apr 4, 2022 at 12:09 AM Heinrich Schuchardt wrote:
>
> Am 3. April 2022 23:08:33 MESZ schrieb Kyle Evans :
> > On Tue, Jan 12, 2021 at 1:59 PM Heinrich Schuchardt
> > wrote:
> >>
> >> Up to now the bootefi command used the last file loaded to determi
isk information this way
and I have to drive it manually, but that's still orders of magnitude
better than having to locally shuffle new loader.efis onto a flash
drive and keep moving the flash drive back and forth to iterate on it.
Thans,
Kyle Evans
On Wed, May 13, 2020 at 7:13 AM Matthias Brugger wrote:
>
> On 26/02/2020 22:39, kev...@freebsd.org wrote:
> > From: Kyle Evans
> >
> > Some systems may use a slightly larger stub to do PSCI for booting the RPi
> > family. The number of pages has been made
On Wed, Feb 26, 2020 at 3:38 PM wrote:
>
> From: Kyle Evans
>
> While the nearly-universal default for the Raspberry Pi family is to use
> spin tables and the spin table implementation provided by the Raspberry Pi
> Foundation, FreeBSD and others may use a PSCI impl
On Wed, Feb 26, 2020 at 12:26 PM Kyle Evans wrote:
>
> On Wed, Feb 26, 2020 at 12:06 PM Matthias Brugger wrote:
> >
> >
> >
> > On 26/02/2020 15:03, kev...@freebsd.org wrote:
> > > From: Kyle Evans
> > >
> > > The psci stub provided by
On Wed, Feb 26, 2020 at 12:06 PM Matthias Brugger wrote:
>
>
>
> On 26/02/2020 15:03, kev...@freebsd.org wrote:
> > From: Kyle Evans
> >
> > The psci stub provided by Raspberry Pi is around 5k in size, thus residing
> > in the first two pages of memory. With
I have a build error using mainline/master.
drivers/ddr/imx/imx8m/ddr4_init.c:11:10: fatal error:
asm/arch/imx8m_ddr.h: No such file or directory
I don't find the file in u-boot or u-boot-imx tree's.
-Kyle
___
U-Boot mailing list
U-Boot@lists.denx.de
h
On Wed, Apr 18, 2018 at 8:55 AM, Peter Robinson wrote:
> On Wed, Apr 18, 2018 at 2:16 PM, Kyle Evans wrote:
>> On Wed, Feb 14, 2018 at 5:02 PM, wrote:
>>> The Pine64 has a known issue on gigabit links (see [1]); some boards suffer
>>> significant packet loss on Gig
t; undocumented stuff.
>
> [1] https://forum.pine64.org/showthread.php?tid=835&pid=19704#pid19704
>
> Kyle Evans (2):
> net: phy: Add PHY_RTL8211E_PINE64_GIGABIT_FIX for realtek phys
> Configs: Use the newly added PHY_RTL8211E_PINE64_GIGABIT_FIX
>
> configs/pine6
On Thu, Feb 15, 2018 at 3:32 PM, André Przywara wrote:
> Hi,
>
> thanks for picking this up!
>
> (CC:ing Icenowy, who was engaged in a Linux fix for this issue last year
> [2][3]. It's Chinese New Year though, so not sure how quickly she will
> answer).
>
> On 14/02/18 23:02, kev...@freebsd.org wr
On Tue, Jan 23, 2018 at 4:18 PM, Samuel Holland wrote:
> These nodes were previously in an unused file specific to the Pine64.
> Move them to the base SoC device tree for use by other boards. Require
> individual boards to enable the emac and provide a pin configuration.
>
> Signed-off-by: Samuel
15 matches
Mail list logo
