From: Philip Balister <philip@balister.org>
To: tony@atomide.com
Cc: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: 2.6.19 + omap patch on the OSK
Date: Tue, 02 Jan 2007 16:02:38 -0500 [thread overview]
Message-ID: <459AC86E.7030802@balister.org> (raw)
In-Reply-To: <20070102201156.GA9733@atomide.com>
tony@atomide.com wrote:
> * Philip Balister <philip@balister.org> [070102 12:03]:
>> I just built a 2.6.19 + omap patch kernel for my OSK. When I tried
>> booting it, the kernel oopsed when it started ALSA. Has anyone booted an
>> OSK using this kernel version?
>
> This is probably because of the zero byte scan missing from linux-omap
> tree as we're trying to sync things with mainline.
>
> Please try this patch:
>
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-October/008232.html
>
> I'll apply it back to linux-omap tree as now there is a longer term
> solution with David Brownell's I2C patches that should eventually
> solve this problem for mainline kernel also.
Adding this patch resolved my problem.
Thanks,
Philip
next prev parent reply other threads:[~2007-01-02 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 19:56 2.6.19 + omap patch on the OSK Philip Balister
2007-01-02 20:11 ` tony
2007-01-02 21:02 ` Philip Balister [this message]
2007-01-03 17:08 ` Dirk Behme
2007-01-03 17:26 ` Tony Lindgren
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=459AC86E.7030802@balister.org \
--to=philip@balister.org \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.com \
/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