Grüüzzi
This part (now named linux16) is kept for backward compatibility only.
And it looks like current implementation of linux command doesn't suffer
this limitation. Can you confirm?
BTW I'm at ETH too
Jan Alsenz wrote:
Robert Millan wrote:
On Tue, Feb 10, 2009 at 07:02:56PM +0100, Jan Als
Robert Millan wrote:
> On Tue, Feb 10, 2009 at 07:02:56PM +0100, Jan Alsenz wrote:
>> Hello!
>>
>> I just noticed, that the pc linux loader (loader/i386/pc/linux.c) always
>> truncates the kernel command line to less than 256 characters.
>> Well since I needed a longer command line, I fixed this pr
On Tue, Feb 10, 2009 at 07:02:56PM +0100, Jan Alsenz wrote:
> Hello!
>
> I just noticed, that the pc linux loader (loader/i386/pc/linux.c) always
> truncates the kernel command line to less than 256 characters.
> Well since I needed a longer command line, I fixed this problem.
Hi,
Thanks for you
Hi again!
I checked the boot protocol documentation and found that since version
2.06 (kernel 2.6.22) there is a field with the supported command line size.
I updated my patch to respect this field if it is present, otherwise the
maximum 4k buffer is used.
Greets,
Jan
Jan Alsenz schrieb:
> He
Hi!
I also don't know the exact details, it sure would be better to have some kind
of detection!
But the limit I set is not that arbitrary:
--- Quote from Documentation/kernel-parameters.txt ---
The number of kernel parameters is not limited, but the length of the
complete command line (parameter
Hello!
I don't know the linux booting protocol in details but it looks like you
patch replaces one arbitrary limit (256) by another (4096). Is there any
way of avoiding any arbitrary limit at all wothout modyfiing boot protocol?
Thanks
Vladimir 'phcoder' Serbinenko
Jan Alsenz wrote:
Hello!
I
