linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Olaf Hering <olh@suse.de>,
	linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
	Greg KH <greg@kroah.com>
Subject: Re: [PATCH] simple class for adb
Date: Sat, 1 May 2004 21:07:25 -0700	[thread overview]
Message-ID: <20040502040724.GA11529@pants.nu> (raw)
In-Reply-To: <1083450972.29595.203.camel@gaston>


On Sun, May 02, 2004 at 08:36:12AM +1000, Benjamin Herrenschmidt wrote:
> I'm not sure I want to keep /dev/adb forever.... This is at best a
> workaround so that udev creates it. Ultimately, we want a real adb
> bus in the device-model and a different mecanism to send special
> commands to the system controller. I think somebody from the m68k
> folks is already working on the ADB bus stuff though.

Slowly but surely, yes. Although perhaps just slowly. I've got part
of it written, but I haven't had any time the last month or so due
to my real job. I will probably have more time to finish up the
new ADB subsystem later this month.

I definitely agree on getting rid of most of the reasons for
/dev/adb, but I'm not sure what all people use through it. I know
the trackpad tool uses it, but I'm not sure of anything else.
Does the sleep stuff use /dev/adb or /dev/pmu?

	Brad Boyer
	flar@allandria.com


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

  reply	other threads:[~2004-05-02  4:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-01 18:26 [PATCH] simple class for adb Olaf Hering
2004-05-01 22:36 ` Benjamin Herrenschmidt
2004-05-02  4:07   ` Brad Boyer [this message]
2004-05-02 17:12     ` Cedric Pradalier
2004-05-02  8:14 ` Geert Uytterhoeven
2004-05-04 20:58 ` Greg KH

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=20040502040724.GA11529@pants.nu \
    --to=flar@allandria.com \
    --cc=benh@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olh@suse.de \
    /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).