From: Ben Dooks <ben@fluff.org>
To: Uli Luckas <u.luckas@road.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
adaplas@gmail.com, David Brownell <david-b@pacbell.net>,
Linux I2C <i2c@lm-sensors.org>
Subject: Re: [i2c] Frame buffers and early i2c
Date: Tue, 10 Jun 2008 11:02:50 +0100 [thread overview]
Message-ID: <20080610100249.GA30539@fluff.org.uk> (raw)
In-Reply-To: <200806101131.19763.u.luckas@road.de>
On Tue, Jun 10, 2008 at 11:31:19AM +0200, Uli Luckas wrote:
> On Tuesday, 10. June 2008, Jean Delvare wrote:
> > Hi Uli,
> >
> > On Mon, 9 Jun 2008 23:59:35 +0200, Uli Luckas wrote:
> > > On Monday 09 June 2008, Jean Delvare wrote:
> > > > Why don't you ask on the i2c mailing list? Cc added.
> > >
> > > I wanted to get i2c developers plus frame buffer and other i2c client
> > > developers involved. Crossposting to more then 2 lists seemed wrong.
> >
> > So you prefer to post to one random list than the two lists where your
> > target audience is? Interesting approach. If you really don't want to
> > post to two lists at once, just send two separate posts?
> >
> And have two seperate threads of communication??? lfml is where they all are
> and avery maintainer has different preferences. Anyway, I got your point and
> will come to the i2c list in the future if you prefere.
>
> > > I'll change the pxa i2c driver to subsys_initcall and try if that works
> > > when I get back to my desk tomorrow.
> >
> > I expect it to work, as apparently other platforms are doing exactly
> > that already.
> >
> Just changing the initcall to subsys really did the trick. I thought, this was
> the first thing I tried and I thought it crashed my device. But obviousely I
> had some other problem.
> If Russell gives his Ack, could this be pushed upstream through i2c?
Does this work if the code is built as a module?
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.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2008-06-10 10:02 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 ` Ben Dooks [this message]
2008-06-10 10:18 ` [i2c] " Jean Delvare
2008-06-10 11:47 ` Uli Luckas
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=20080610100249.GA30539@fluff.org.uk \
--to=ben@fluff.org \
--cc=adaplas@gmail.com \
--cc=david-b@pacbell.net \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=u.luckas@road.de \
/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