public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Komal Shah <komal_shah802003@yahoo.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: I2C zero length transfers and SMBUS_QUICK, was: Pending October patches
Date: Mon, 06 Nov 2006 11:36:08 +0100	[thread overview]
Message-ID: <85d580lv53.fsf@orfeo.duckcorp.org> (raw)
In-Reply-To: <20061105194915.12776.qmail@web37903.mail.mud.yahoo.com> (Komal Shah's message of "Sun, 5 Nov 2006 11:49:15 -0800 (PST)")


Hi,

Komal Shah <komal_shah802003@yahoo.com> writes:

> --- Dirk Behme <dirk.behme@googlemail.com> wrote:
>
>
>> >>Komal, what do you think here?
>> >>
>> >>Anybody aware of someone working on a better solution? Any 
>> >>link to the LKML discussion about this?
>> >>
>> > Few links:
>> ...
>> >
>>
> http://linux.omap.com/pipermail/davinci-linux-open-source/2006-October/001332.html
>> 
>> Sounds to me a clean fix (new I2C stack?) will need some 
>> decades, if it comes at all. So, how to go one here?
>> 
>> Our hack to make things work on OMAP will not be accepted 
>> upstream. But staying with broken OMAP features only because 
>> (available) hack isn't acceptable in mainline doesn't sound 
>> like an option as well.
>> 
>> I personally vote for working OMAP ;)
>> 
>
> Yes, we need working OMAPs and I don't know if it already broke n770
> too. Let's see what Tony thinks about maintaining this fix in OMAP tree.
>
hmm... well... while taking care of the n770 is nice, I'm not sure that
you should take it into account. 

Brief explanation : 
the current kernel is broken on the n770. It won't even build.

Long explanation :
There are some obvious breakages that are not fixed. For instance, look
at the omap-hw patch I sent. I have some other patches for the build but
the kernel is oopsing later in the boot stage when udev plays with the
uevents in the spi layer... And there are probably more breakages :(


Regards,
Arnaud

  reply	other threads:[~2006-11-06 10:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 15:54 Pending October patches Dirk Behme
2006-11-01 21:28 ` tony
2006-11-02 17:00   ` Dirk Behme
2006-11-03 10:50     ` Komal Shah
2006-11-05 10:32       ` I2C zero length transfers and SMBUS_QUICK, was: " Dirk Behme
2006-11-05 19:49         ` Komal Shah
2006-11-06 10:36           ` Arnaud Patard [this message]
2006-11-06 18:33             ` Broken N770, was: I2C zero length transfers and SMBUS_QUICK Dirk Behme
2006-11-06 19:49               ` Arnaud Patard
2006-11-06 20:18                 ` Broken N770 Dirk Behme
2006-11-06 20:24                   ` Arnaud Patard
2006-11-06  1:37         ` I2C zero length transfers and SMBUS_QUICK, was: Pending October patches David Brownell
2006-11-07 17:40           ` tony
2006-11-07 20:24             ` I2C zero length transfers and SMBUS_QUICK David Brownell
2006-11-09  2:32               ` Tony Lindgren
2006-11-03 19:52   ` Pending October patches David Brownell
2006-11-03 20:18     ` Dirk Behme

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=85d580lv53.fsf@orfeo.duckcorp.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=komal_shah802003@yahoo.com \
    --cc=linux-omap-open-source@linux.omap.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