linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Egger <degger@tarantel.rz.fh-muenchen.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Daniel Egger <degger@fhm.edu>, Dustin Lang <dalang@cs.ubc.ca>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Re:No backlight control on PowerBook G4
Date: Thu, 6 Nov 2003 09:01:32 +0100	[thread overview]
Message-ID: <20031106090132.B18367@tarantel.rz.fh-muenchen.de> (raw)
In-Reply-To: <1068078504.692.175.camel@gaston>

On Thu, Nov 06, 2003 at 11:28:25AM +1100, Benjamin Herrenschmidt wrote:

> > Just checked. It doesn't work with the  latest (Linus) 2.6-test and
> > radeonfb. Do you have any special patches in your tree for radeonfb?
 
> No, I told you to use _my_ 2.6 tree which contains a new radeonfb
> that have not yet been merged upstream.

I noticed that, however I do not have the bandwitdh to track several trees
simultaneously. Will do that on a high bandwidth machine and create a diff.

> bk://ppc.bkbits.net/linuxppc-2.5-benh or rsync from
> source.mvista.com::linuxppc-2.5-benh
 
> Yaboot normally loads a plain vmlinux, though if you are using tftp, you
> need to modify yaboot to be able to d/l more than 4Mb (edit fs_of.c and
> change the allocated size). 

This is probably it. The raw image is just a bit over 4 megs. Is there a
chance that this will change upstream? Also a warning would be nice while
creating the kernel as I'm probably not the only one experiencing this.

> The ELF image should work, at least the
> one produced by my tree does, it's possible that there's a similar size
> problem with the one in Linus tree, a few of those recent changes haven't
> yet made it to Linus.

Size problem? At least it's not triggered by the yaboot limitation because
the image is similar in size to zImage.chrp which would be around 1.8 megs.

--
Servus,
       Daniel

  reply	other threads:[~2003-11-06  7:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-02 19:23 No backlight control on PowerBook G4 Dustin Lang
2003-11-03  0:45 ` Benjamin Herrenschmidt
2003-11-03  8:51   ` Dustin Lang
2003-11-03  9:04     ` Benjamin Herrenschmidt
2003-11-03 16:57   ` Daniel Egger
2003-11-03 21:54     ` Benjamin Herrenschmidt
2003-11-04 10:43       ` Daniel Egger
2003-11-04 20:05       ` Daniel Egger
2003-11-06  0:28         ` Benjamin Herrenschmidt
2003-11-06  8:01           ` Daniel Egger [this message]
2003-11-06  8:16             ` Dustin Lang
2003-11-06  8:26             ` Benjamin Herrenschmidt
2003-11-06  9:36               ` Daniel Egger
2003-11-07  9:50           ` Daniel Egger
2003-11-09  2:59             ` Benjamin Herrenschmidt
2003-11-09  9:55               ` Daniel Egger
2003-11-09 11:03                 ` Benjamin Herrenschmidt

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=20031106090132.B18367@tarantel.rz.fh-muenchen.de \
    --to=degger@tarantel.rz.fh-muenchen.de \
    --cc=benh@kernel.crashing.org \
    --cc=dalang@cs.ubc.ca \
    --cc=degger@fhm.edu \
    --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;
as well as URLs for NNTP newsgroup(s).