From: Brad Boyer <flar@allandria.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux/m68k on Mac <linux-mac68k@mac.linux-m68k.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: drivers/macintosh/Kconfig (was: Re: Linux 2.6.3-rc1)
Date: Sun, 8 Feb 2004 15:05:08 -0800 [thread overview]
Message-ID: <20040208230508.GA14393@pants.nu> (raw)
In-Reply-To: <1076278954.27930.98.camel@gaston>
On Mon, Feb 09, 2004 at 09:22:35AM +1100, Benjamin Herrenschmidt wrote:
> I agree that the abuse of adb_request should go, though replacing
> it isn't easy at this stage. It's not worth bothering with a
> common interface for things like poweroff, reset and RTC imho,
> it would only solve a small part of the problem, there are too
> many places where we actually need to send directly a PMU command.
Based on my reading of the code, most of the places sending PMU
commands directly are actually calling pmu_request, so I was
planning on leaving that alone as a hook directly into the PMU
driver, and although it's related to ADB, it isn't going through
the current ADB framework, either.
> Part of the problem is that the PMU driver low level state machine
> it tied to the format of the adb_request structure. I don't think
> I will fix any of that for 2.6. For 2.7, I may define a low level
> pmu_request structure _without_ embedded buffers and have the ADB
> request handling allocate one of those atomically.
I don't see where that is an issue. The PMU driver internally can
continue to be based on the same structure, and interface with
the new ADB layer just for ADB messages. I suppose it will be clearer
once I get that part of the code finished. I've been concentrating
more on the 68k side of things for this, since I don't care if I
confuse one of my older boxes.
Brad Boyer
flar@allandria.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-08 23:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0402061823040.30672@home.osdl.org>
2004-02-08 14:25 ` drivers/macintosh/Kconfig (was: Re: Linux 2.6.3-rc1) Geert Uytterhoeven
2004-02-08 14:53 ` David D. Kilzer
2004-02-08 19:32 ` Geert Uytterhoeven
2004-02-08 20:57 ` Brad Boyer
2004-02-08 21:15 ` [linux-mac68k] " David D. Kilzer
2004-02-08 22:16 ` Geert Uytterhoeven
2004-02-08 23:00 ` David D. Kilzer
2004-02-08 21:29 ` Benjamin Herrenschmidt
2004-02-08 21:59 ` Brad Boyer
2004-02-08 22:22 ` Benjamin Herrenschmidt
2004-02-08 23:05 ` Brad Boyer [this message]
2004-02-08 22:07 ` [linux-mac68k] " Matthias Urlichs
2004-02-08 22:19 ` Brad Boyer
2004-02-08 22:25 ` Benjamin Herrenschmidt
2004-02-08 22:39 ` Matthias Urlichs
2004-02-08 21:26 ` Benjamin Herrenschmidt
2004-02-08 22:07 ` Geert Uytterhoeven
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=20040208230508.GA14393@pants.nu \
--to=flar@allandria.com \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mac68k@mac.linux-m68k.org \
--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).