linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Tobler <toa@pop.agri.ch>
To: jlquinn@us.ibm.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Building 2.3.35?
Date: Thu, 06 Jan 2000 16:38:49 +0100	[thread overview]
Message-ID: <3874B709.86897215@pop.agri.ch> (raw)
In-Reply-To: 8525685E.0054AAAB.00@D51MTA03.pok.ibm.com




jlquinn@us.ibm.com wrote:
> 
> I tried to build the standard 2.3.35 kernel without success.  Does anyone
> know what's going on?
> 
> I'm building a kernel for powermac only and having problems with irq_offset
> not being a member of
> struct hw_interrupt_info(?).  In particular, arch/ppc/kernel/open_pic.c
> doesn't build in this kernel.  The struct is defined in include/linux/irq.h
> and doesn't have this field.  Also, to my uninformed eye, pmacs don't even
> require open_pic.c
> 
> In 2.2.13, irq_offset is a member of struct hw_interrupt_info, which is
> declared in arch/ppc/kernel/local_irq.h.  So obviously this struct was
> deemed to be useful to other architectures but in the meantime, this field
> was removed.
> 
> I've tried to untangle this enough to build, but haven't succeeded so far.

The problem is known and Cort replied me yesterday that he is working on
that. He said maybe in the next one or two versions it should be fixed.
AFAIK the latest working 2.3.X kernel was the 2.3.29 from
linuxcare.com.au.
All other higher kernel I got to build but not to boot.

Have you other experiences?

Andreas
-- 
| Andreas Tobler				
| CH-8004 Zuerich 							
| E-Mail: andreas.tobler@alcatel.ch	| a.tobler@schweiz.ch
-----------------------------------------------------------

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-01-06 15:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-06 15:25 Building 2.3.35? jlquinn
2000-01-06 15:38 ` Andreas Tobler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-01-06 15:49 jlquinn
2000-01-06 16:19 ` Benjamin Herrenschmidt
2000-01-06 20:17   ` Geert Uytterhoeven
2000-01-06 20:21     ` Larry McVoy

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=3874B709.86897215@pop.agri.ch \
    --to=toa@pop.agri.ch \
    --cc=jlquinn@us.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.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).