From: Al Viro <viro@ftp.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH 2/3] m68k: compile fix - ADBREQ_RAW missing declaration
Date: Thu, 15 Dec 2005 18:14:05 +0000 [thread overview]
Message-ID: <20051215181405.GB27946@ftp.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.62.0512151858100.6884@pademelon.sonytel.be>
On Thu, Dec 15, 2005 at 07:00:54PM +0100, Geert Uytterhoeven wrote:
> Even if behavior is unchanged, this doesn't mean that people like their code
> being modified behind their back...
>
> Anyway, last time I tried to bring this up with the union of Mac and PowerMac
> guys, no one seemed to remember why ADBREQ_RAW was really needed...
>From my reading of the code it's a way for mac/misc.c to send a packet that
starts with CUDA_PACKET or PMU_PACKET instead of ADB_PACKET, but otherwise
is the same as normal adb_request() ones...
Used for access to timer, nvram, etc. - looks like that puppy used to
use the same protocol for more than just ADB and the first byte of packet
really selects the destination...
next prev parent reply other threads:[~2005-12-15 18:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 8:55 [PATCH 2/3] m68k: compile fix - ADBREQ_RAW missing declaration Al Viro
2005-12-15 12:00 ` Roman Zippel
2005-12-15 17:16 ` Al Viro
2005-12-15 17:47 ` Al Viro
2005-12-15 17:54 ` Geert Uytterhoeven
2005-12-16 1:21 ` Finn Thain
2005-12-15 17:51 ` Roman Zippel
2005-12-15 17:55 ` Al Viro
2005-12-15 18:00 ` Geert Uytterhoeven
2005-12-15 18:14 ` Al Viro [this message]
2005-12-15 18:58 ` Al Viro
2005-12-15 20:05 ` Brad Boyer
2005-12-22 5:06 ` Al Viro
2005-12-25 2:26 ` Brad Boyer
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=20051215181405.GB27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zippel@linux-m68k.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