mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: David Eger <eger@havoc.gtf.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pmac_zilog: initialize port spinlock on all init paths
Date: Fri, 16 Jul 2004 13:50:56 -0700	[thread overview]
Message-ID: <20040716205056.GY21856@smtp.west.cox.net> (raw)
In-Reply-To: <20040716201515.GA14095@havoc.gtf.org>

On Fri, Jul 16, 2004 at 04:15:15PM -0400, David Eger wrote:

> On Wed, Jul 14, 2004 at 04:39:20PM -0700, Tom Rini wrote:
> > On Wed, Jul 14, 2004 at 12:04:03AM -0400, David Eger wrote:
> > > > > ( of course, it still spews diahrea of 'IN from bad port XXXXXXXX'
> > > > >   but then, I don't have the hardware.... still, seems weird that OF
> > > > >   would report that I do have said hardware :-/ )
> > > > 
> > > > The IN from bad port is a different issue, it's probably issued by
> > > > another driver trying to tap legacy hardware, either serial.o or
> > > > ps/2 kbd, I suppose, check what else of that sort you have in your
> > > >  .config
> > > 
> > > Sure enough, the "IN from bad port XXXXXXXX" ended up being the i8042
> > > serial PC keyboard driver, enabled with CONFIG_SERIO_I8042.  Don't know
> > > why that's in ppc defconfig....
> > 
> > That's on for all of the ppc boards with an i8042 which the defconfig is
> > supposed to support (prep & chrp hardware).
> 
> Sorry, I tend to think "ppc == pmac".  So, a couple of thoughts:
> 
> (1) Can you make the i8042 disable itself if the hardware isn't there?
>     Those damned bad port messages eat my entire syslog buffer.

Ask Vojtech Pavlik.

> (2) At the moment, that defconfig is also shared by us TiBook hackers.
>     Would it be feasible to have a separate pmac_defconfig?  How do 
>     'make menuconfig' and friends choose a defconfig if there isn't a .config?

One already exists.  The short answer is that when .config doesn't
exist, we look at /boot/config-`uname -r` and then
arch/$(ARCH)/defconfig.  I believe the that 'make help' mentions the
next neat trick.  If you do 'make pmac_defconfig' for example,
arch/ppc/configs/pmac_defconfig is used as the base of a new .config
file, with all options not documented in that file being set to 'n'.
You can then either build the kernel, or further tweak via
menuconfig/etc.

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2004-07-16 20:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12  7:51 pmac oops: devfs versus power management - fight! David Eger
2004-07-12  8:21 ` oops: pmac power management David Eger
2004-07-12 22:09   ` pmac_zilog: driver loads (and crashes) without hardware David Eger
2004-07-13  0:39     ` [PATCH] pmac_zilog: initialize port spinlock on all init paths David Eger
2004-07-13  4:16       ` Benjamin Herrenschmidt
2004-07-14  4:04         ` David Eger
2004-07-14 23:39           ` Tom Rini
2004-07-16 20:15             ` David Eger
2004-07-16 20:50               ` Tom Rini [this message]
2004-07-19 15:51               ` Anton Blanchard
2004-07-16 18:58         ` [PATCH] pmac_zilog: insert correct failure path for device numbers being taken David Eger
2004-07-16 19:01           ` Benjamin Herrenschmidt
2004-07-17 13:07           ` [PATCH] pmac_zilog: fix patch drain bramage David Eger
     [not found] <200407141709.i6EH9EYW029131@hera.kernel.org>
2004-07-14 19:27 ` [PATCH] pmac_zilog: initialize port spinlock on all init paths Hollis Blanchard

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=20040716205056.GY21856@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=benh@kernel.crashing.org \
    --cc=eger@havoc.gtf.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®