Jens Thiele writes:
> I think you are at debconf - maybe we could meet there?
For the archive: we did meet there.
Karsten Merker wrote a fine summary on the debian-arm mailing list in
Message-ID: <20150911181300.ga7...@excalibur.cnev.de>
https://lists.debian.org/msgid-search/20150911181300.ga7..
sorry, for digging out that old thread, but i never got an answer to
this one.
I think you are at debconf - maybe we could meet there?
Jens Thiele writes:
> Karsten Merker writes:
>
>> Ah, so the configuration happens via specific build-time config
>> options and not via the u-boot environment
Karsten Merker writes:
> Ah, so the configuration happens via specific build-time config
> options and not via the u-boot environment. In that case,
> building additional variants would of course work rather easily
> by defining additional targets, but we would end up with a really
> large numbe
Karsten Merker writes:
> On Fri, Jun 26, 2015 at 11:06:05AM +0200, Jens Thiele wrote:
>
>> The specific u-boot environment is needed for the lcd display
>> settings/timings. Would it be an option to build different u-boot
>> configurations for the different board+display combinations?
>
> AFAICS
On Sun, 2015-06-21 at 19:01 +0200, Karsten Merker wrote:
>
> > What about adding support in debian-installer to dsisplay on both the
> > serial console and framebuffer?
>
> My memory on that topic is unfortunately a bit shady, but IIRC
> this was proposed some time ago already and was dismissed
not a direct answer to your mail but very related and raising other
questions / problems:
jessie kernel already supports simplefb (simple framebuffer) together
with newer u-boot, specific u-boot environment and a custom device tree
it is possible to get a framebuffer.
The specific u-boot environm
On Sun, Jun 21, 2015 at 10:07:17PM +0200, Geert Stappers wrote:
> On Sun, Jun 21, 2015 at 05:52:20PM +0200, Karsten Merker wrote:
> > Hello everybody,
>
> Hi,
>
>
>
> > AFAICS there is no way to determine the "active" console in
> > u-boot and set either the u-boot console variable or the
> > s
On Sun, Jun 21, 2015 at 05:52:20PM +0200, Karsten Merker wrote:
> Hello everybody,
Hi,
> AFAICS there is no way to determine the "active" console in
> u-boot and set either the u-boot console variable or the
> stdout-path property accordingly. Even if there was such a
> mechanism, the question
Hi,
Karsten Merker (2015-06-21):
> On Sun, Jun 21, 2015 at 09:17:12AM -0700, Vagrant Cascadian wrote:
>
> > On 2015-06-21, Karsten Merker wrote:
> > > If we don't pass a console variable to the kernel, d-i starts
> > > on the console device defined by the platform's stdout-path
> > > property, i
On 2015-06-21, Karsten Merker wrote:
> If we don't pass a console variable to the kernel, d-i starts
> on the console device defined by the platform's stdout-path
> property, i.e. usually on a serial console - again bad luck
> for people having only a framebuffer console.
>
> If we set the console
10 matches
Mail list logo
