From: Andres Salomon <dilinger@queued.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Chris Ball <cjb@laptop.org>,
Harvey Harrison <harvey.harrison@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] olpc: fix model detection without OFW
Date: Sat, 14 Feb 2009 17:32:37 -0500 [thread overview]
Message-ID: <20090214173237.29407661@ephemeral> (raw)
In-Reply-To: <20090214221429.GB5200@elte.hu>
On Sat, 14 Feb 2009 23:14:29 +0100
Ingo Molnar <mingo@elte.hu> wrote:
[...]
> Where did my git grepping skills go wrong?
>
> I git-grepped the code and this is the scope i found:
>
> olpc_platform_info.boardrev is used for:
>
> - a printk
> - olpc_board_at_least() which is used in:
> - drivers/input/mouse/hgpk.c: mouse driver quirk
> - sound/pci/cs5535audio/cs5535audio_olpc.c: audio quirk
>
> aha. I missed this roundabout impact:
>
> - arch/x86/kernel/olpc.c: OLPC_F_DCON flag
> - which is used in olpc_has_dcon(), which is used in:
> - drivers/video/geode/gxfb_core.c: GX modes db
> [ouch if this goes
> wrong!]
> - drivers/video/geode/lxfb_core.c: ditto
>
> So i guess the mouse and audio quirk point was correct too, but the
> major impact is the graphics mode array mismatch and the resulting
> nonsensical mode setting, right?
>
> Ingo
Yep.
prev parent reply other threads:[~2009-02-14 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 22:20 [PATCH] olpc: fix endian bug in openfirmware workaround Harvey Harrison
2008-09-24 7:53 ` Ingo Molnar
2009-02-14 1:56 ` [PATCH] olpc: fix model detection without OFW Chris Ball
2009-02-14 4:19 ` Andres Salomon
2009-02-14 21:43 ` Ingo Molnar
2009-02-14 21:53 ` Andres Salomon
2009-02-14 22:14 ` Ingo Molnar
2009-02-14 22:32 ` Andres Salomon [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=20090214173237.29407661@ephemeral \
--to=dilinger@queued.net \
--cc=akpm@linux-foundation.org \
--cc=cjb@laptop.org \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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