On Mon, Jun 22, 2020 at 02:03:28PM -0700, H. Peter Anvin wrote:
> On 2020-06-22 14:01, Tom Rini wrote:
> >
> > I'm picky here because, well, there's a whole lot of moving parts in the
> > pre-kernel world. In a strict sense, "UEFI" doesn't do anything with
> > the kernel but based on hpa's commen
On Mon, Jun 22, 2020 at 01:48:45PM -0700, H. Peter Anvin wrote:
> On 2020-06-22 13:40, Tom Rini wrote:
> > On Mon, Jun 22, 2020 at 01:02:16PM -0700, ron minnich wrote:
> >
> >> The other thing you ought to consider fixing:
> >> initrd is documented as follows:
> >>
> >> initrd= [BO
On 2020-06-22 14:01, Tom Rini wrote:
>
> I'm picky here because, well, there's a whole lot of moving parts in the
> pre-kernel world. In a strict sense, "UEFI" doesn't do anything with
> the kernel but based on hpa's comments I assume that at least the
> in-kernel UEFI stub does what Documentatio
On Mon, Jun 22, 2020 at 01:56:24PM -0700, ron minnich wrote:
> So, let me first add, the comment can be removed as needed. Comments
> offered only for clarification.
Noted, thanks.
> On Mon, Jun 22, 2020 at 1:40 PM Tom Rini wrote:
>
> > But what do you mean UEFI "consumes" initrd= ?
>
> What
So, let me first add, the comment can be removed as needed. Comments
offered only for clarification.
On Mon, Jun 22, 2020 at 1:40 PM Tom Rini wrote:
> But what do you mean UEFI "consumes" initrd= ?
What I mean is, there are bootloaders that will, if they see initrd=
in the command line, remove
On 2020-06-22 13:40, Tom Rini wrote:
> On Mon, Jun 22, 2020 at 01:02:16PM -0700, ron minnich wrote:
>
>> The other thing you ought to consider fixing:
>> initrd is documented as follows:
>>
>> initrd= [BOOT] Specify the location of the initial ramdisk
>>
>> for bootloaders only.
>>
On Mon, Jun 22, 2020 at 01:02:16PM -0700, ron minnich wrote:
> The other thing you ought to consider fixing:
> initrd is documented as follows:
>
> initrd= [BOOT] Specify the location of the initial ramdisk
>
> for bootloaders only.
>
> UEFI consumes initrd from the command line
On June 19, 2020 5:03:33 PM PDT, ron minnich wrote:
>It seems fine to me, but I did not initially object to the use of that
>name anyway. hpa, what do you think?
>
>On Fri, Jun 19, 2020 at 7:31 AM Tom Rini wrote:
>>
>> Most architectures have been passing the location of an initrd via
>the
>> ini
The other thing you ought to consider fixing:
initrd is documented as follows:
initrd= [BOOT] Specify the location of the initial ramdisk
for bootloaders only.
UEFI consumes initrd from the command line as well. As ARM servers
increasingly use UEFI, there may be situations in whi
It seems fine to me, but I did not initially object to the use of that
name anyway. hpa, what do you think?
On Fri, Jun 19, 2020 at 7:31 AM Tom Rini wrote:
>
> Most architectures have been passing the location of an initrd via the
> initrd= option since their inception. Remove the comment as it'
Most architectures have been passing the location of an initrd via the
initrd= option since their inception. Remove the comment as it's both
wrong and unrelated to the commit that introduced it.
Fixes: 694cfd87b0c8 ("x86/setup: Add an initrdmem= option to specify initrd
physical address")
Cc: An
11 matches
Mail list logo
