public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Uli Luckas <u.luckas@road.de>
To: i2c@lm-sensors.org
Cc: Ben Dooks <ben@fluff.org>, David Brownell <david-b@pacbell.net>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	LKML <linux-kernel@vger.kernel.org>,
	adaplas@gmail.com
Subject: Re: [i2c] Frame buffers and early i2c
Date: Tue, 10 Jun 2008 13:47:30 +0200	[thread overview]
Message-ID: <200806101347.31003.u.luckas@road.de> (raw)
In-Reply-To: <20080610100249.GA30539@fluff.org.uk>


On Tuesday, 10. June 2008, Ben Dooks wrote:
> BTW, if people do have these sort of dependencies, then modules
> are another way of sorting out the load order, unless you have
> the module autoload enabled.
>
True. But my original post stated:
> In order to use the frame buffer console I have i2c and pxafb compiled in
This is one example where waiting for user space to be up and running is not 
an option.

regards,
Uli

-- 

------- ROAD ...the handyPC Company - - -  ) ) )

Uli Luckas
Software Development

ROAD GmbH
Bennigsenstr. 14 | 12159 Berlin | Germany
fon: +49 (30) 230069 - 64 | fax: +49 (30) 230069 - 69
url: www.road.de

Amtsgericht Charlottenburg: HRB 96688 B
Managing directors: Hans-Peter Constien, Hubertus von Streit

  parent reply	other threads:[~2008-06-10 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200806091647.42757.u.luckas@road.de>
2008-06-09 18:52 ` Frame buffers and early i2c Jean Delvare
     [not found]   ` <20080609205212.4b0f1ba6-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-09 21:59     ` Uli Luckas
2008-06-10  6:25       ` Jean Delvare
2008-06-10  9:31         ` Uli Luckas
2008-06-10 10:02           ` [i2c] " Ben Dooks
2008-06-10 10:18             ` Jean Delvare
2008-06-10 11:47             ` Uli Luckas [this message]
2008-06-10 10:57           ` Jean Delvare

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=200806101347.31003.u.luckas@road.de \
    --to=u.luckas@road.de \
    --cc=adaplas@gmail.com \
    --cc=ben@fluff.org \
    --cc=david-b@pacbell.net \
    --cc=i2c@lm-sensors.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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