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, was: I2C zero length transfers and SMBUS_QUICK
Date: Mon, 06 Nov 2006 20:49:11 +0100 [thread overview]
Message-ID: <85zmb4iceg.fsf@orfeo.duckcorp.org> (raw)
In-Reply-To: <454F7FDF.1080101@gmail.com> (Dirk Behme's message of "Mon, 06 Nov 2006 19:33:03 +0100")
Dirk Behme <dirk.behme@googlemail.com> writes:
> Seems that this is the month of mail subject change ;)
hehe :)
>
> Arnaud Patard (Rtp) wrote:
>> Komal Shah <komal_shah802003@yahoo.com> writes:
>>>Yes, we need working OMAPs and I don't know if it already broke n770
>>>too. ...
>>>
> ...
>> the current kernel is broken on the n770. It won't even build.
>
> 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)
- drivers/cbus/tahvo-usb.c is still using usb_otg.h. Patch not sent but
trivial to write.
>
> However, still some warnings in omap-hw.c (unused
> omap_nand_write_byte),
hmm.. yeah. My fault :(
> retu-user.c, tahvo-user.c,
> tahvo-usb.c (all my new friend "ignoring return value") and
> sti-console.c ("value computed is not used").
>
>> Long explanation :
>> There are some obvious breakages that are not fixed. For instance, look
>> at the omap-hw patch I sent.
>
> It is already applied.
>
>> 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 :(
>
> 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>
But if you want to go a little bit further than the first lines of the
linuxrc file, you have to reintroduce the ioctl MEMSETOOBSEL in
mtdchar.c because the dsme/bme/cal-tools/libcal and friends from nokia
are using it. Unfortunately, when they're failing, they reboot your
device.
[ Playing with the r&d flags from the flasher won't help as the tools are
failing before reading them. ]
>
> Regards
>
> Dirk
Regards,
Arnaud
next prev parent reply other threads:[~2006-11-06 19:49 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 [this message]
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=85zmb4iceg.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