public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Broken N770
Date: Mon, 06 Nov 2006 21:24:01 +0100	[thread overview]
Message-ID: <85odrkiase.fsf@orfeo.duckcorp.org> (raw)
In-Reply-To: <454F9892.2050202@gmail.com> (Dirk Behme's message of "Mon, 06 Nov 2006 21:18:26 +0100")

Dirk Behme <dirk.behme@googlemail.com> writes:

> Arnaud Patard (Rtp) wrote:
>>>Thanks for the hint! With patch previously sent
>>>n770_defconfig should compile again.
>>
>> Sorry, that's wrong. I'm using an up2date git tree with origin
>> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git/
>> and I still need patches.
>>
>> For instance : - there are still some users of pt_regs (patch sent
>> some time ago)
>
> Yes, but these are only warnings and they are already fixed by patch
> sent.
>
> For drivers/usb/core/hub.c I had to use
>
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-November/008254.html

If you look at the full thread, you'll see that I'm using the same patch :)

>
>> - drivers/cbus/tahvo-usb.c is still using usb_otg.h. Patch not sent but
>> trivial to write.
>
> Mmh. For drivers/cbus/tahvo-usb.c my patch contains
>
> --- linux-osk.orig/drivers/cbus/tahvo-usb.c
> +++ linux-osk/drivers/cbus/tahvo-usb.c
> @@ -36,7 +36,7 @@
>  #include <linux/usb_ch9.h>
>  #include <linux/usb_gadget.h>
>  #include <linux/usb.h>
> -#include <linux/usb_otg.h>
> +#include <linux/usb/otg.h>
>  #include <linux/i2c.h>
>  #include <linux/workqueue.h>
>  #include <linux/kobject.h>
>
> What's wrong with this? For me using recent git it compiles. I have no
> usb_otg.h.

No, that's fine. I was talking about that change. As it's not in the current
git tree, I wanted to say that you need such a patch :)

>
>>>Is there any way to test self compiled kernel on N770
>>>without breaking flashed SW/image? Anything like download to
>>>RAM, e.g. used by uboots TFTP download on OSK?
>>
>> yes, there is. That's what I'm using ^^
>>
>> ./flasher-2.0 -l -b -k <my_kernel>
>
> Thanks, will try it.
>
> Cheers
>
> Dirk

Regards,
Arnaud

  reply	other threads:[~2006-11-06 20:24 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
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 [this message]
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=85odrkiase.fsf@orfeo.duckcorp.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=dirk.behme@googlemail.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