From: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] alleged fbset brokenness
Date: Thu, 26 Jul 2007 09:01:31 +0200 [thread overview]
Message-ID: <1185433291.31437.38.camel@localhost.localdomain> (raw)
In-Reply-To: <20070724141320.GC19688@aon.at>
On Tue, 2007-07-24 at 16:13 +0200, Bernhard Fischer wrote:
> On Mon, Jul 23, 2007 at 02:37:16PM +0200, Ulf Samuelsson wrote:
> >m?n 2007-07-23 klockan 13:29 +0200 skrev Bernhard Fischer:
> >> On Mon, Jul 23, 2007 at 02:10:26PM +0200, Ulf Samuelsson wrote:
> >>
> >> >OK, I'll fix that, but AFAIK it is broken in busybox so It needs
> >>
> >> hm? IIRC it builds fine for me. How is it broken?
> >>
> >
> >I do not know the exact details, since I am applying the
> >patches from an internal buildroot for AVR32 generated
> >by someone else which claims it is broken.
> >It might be AVR32 related, or it might be that he is slightly behind
> >in versions.
>
> Looking forward to hear some details about how fbset from busybox-(1.6.1)
> is broken for you.
It does just not work, I am not able to set the timing parameters. The
depth parameter is the only one I have gotten to work with the fbset
supplied by busybox.
This was with 1.6.0, will test with 1.6.1 when I get my buildroot
working again.
--
With kind regards,
Hans-Christian Egtvedt, siv.ing. (M.Sc.)
Applications Engineer - AVR32 System Solutions - Atmel Norway
--
Mvh
Hans-Christian Egtvedt
prev parent reply other threads:[~2007-07-26 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 9:00 [Buildroot] svn commit: trunk/buildroot/package: fbset ulf at uclibc.org
2007-07-23 10:52 ` Bernhard Fischer
2007-07-23 12:10 ` Ulf Samuelsson
2007-07-23 11:29 ` Bernhard Fischer
2007-07-23 12:37 ` Ulf Samuelsson
2007-07-24 14:13 ` [Buildroot] alleged fbset brokenness Bernhard Fischer
2007-07-26 7:01 ` Hans-Christian Egtvedt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1185433291.31437.38.camel@localhost.localdomain \
--to=hcegtvedt@norway.atmel.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox