mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Daniel Drake <dsd@laptop.org>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	chris@printf.net, dsd@gentoo.org
Subject: Re: Kernel for olpc-1.75
Date: Sat, 14 Jun 2014 10:49:06 +0200	[thread overview]
Message-ID: <20140614084905.GB15326@Nokia-N900> (raw)
In-Reply-To: <CAMLZHHRsewk=YqWp_sKULSfqyejgUWcZMjFp-G388xqaQBbg-g@mail.gmail.com>

Hi!

> On Sat, Jun 7, 2014 at 11:53 PM, Pavel Machek <pavel@ucw.cz> wrote:
> > I broke installation on olpc-1.75, and I guess its time for it to
> > start running self-compiled kernel. (It still boots if I hold right
> > game key, but I can no longer control backlight. It does not boot at
> > all by default.)
> >
> > AFAICT, olpc.fth and zImage in the boot/ directory of USB disk should
> > do the trick.
> >
> > Unfortunately, 3.0 based kernels no longer compile with current tools,
> > so I tried this version (3.6 based).
> 
> Sorry but OLPC never progressed beyond shipping 3.0 on this hardware,
> and low-level development only really happens in maintenance mode at
> the moment.

Ok, wip-3.0 branch boots on the hardware. Good so far... but
touchpad does not work... If you have any idea about that...)

Redhat update kernel (yes, I made a mistake of installing that)
has broken backlight controls, and only boots in development
mode. Ideas here would be welcome, too...

> We did almost get a newer version working, but it had some unresolved
> issues that prevented us from shipping it to users. I'm not sure of
> the state of that arm-3.6 branch you are trying but I don't see
> anything wrong in your process. I would try early printascii() calls
> and a serial cable next.
> 
> Mainline won't run on the machine in any kind of usable state without
> quite a bit of work on drivers and DT (which comes from the firmware).
> I did once start on that but didn't manage to get even the initial
> easy patches past the Marvell maintainers :(

Ok, let me try to get machine into semi-working state, and
then I can think about updating kernels...
						Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2014-06-14  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-07 22:53 Pavel Machek
2014-06-09 10:08 ` Daniel Drake
2014-06-09 11:05   ` Pavel Machek
2014-06-14  8:49   ` Pavel Machek [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=20140614084905.GB15326@Nokia-N900 \
    --to=pavel@ucw.cz \
    --cc=chris@printf.net \
    --cc=dsd@gentoo.org \
    --cc=dsd@laptop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®