public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <jesse@cats-chateau.net>
To: Pavel Machek <pavel@suse.cz>, Patrick Mochel <mochel@osdl.org>
Cc: Pavel Machek <pavel@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] New system device API
Date: Tue, 10 Jun 2003 13:27:54 -0500	[thread overview]
Message-ID: <03061013275402.06462@tabby> (raw)
In-Reply-To: <20030609213247.GC508@elf.ucw.cz>

On Monday 09 June 2003 16:32, Pavel Machek wrote:
> Hi!
>
> > > > So? A keyboard controller is not classified as a system device.
> > >
> > > Its not on pci, I guess it would end up as a system device...
> >
> > Huh? Since when is everything that's not PCI a system device? Please read
> > the documentation, esp. WRT system and platform devices.
>
> Oh and btw keyboard controller is used for rebooting machine. Do you
> still say it is not system device?
> 								Pavel

And here I thought it was the reset line on the bus... :-)

There are lots of ways to do that without involving the keyboard. The old way
was just to wire the serial break signal from the UART to the reset line...

Would that suddenly make the serial interfaces system devices?

What about that "wake on lan" business... does that make the network card a
"system  device"?

The only things I think of as "system device" is the CPU, the memory bus, and
sometimes a thing called a system controller/bus arbiter. The memory bus 
should provide access to any ROM needed for initial program storage.

Outside of that, everything is a peripheral, and should be treated as such,
even though the memory management unit is considered part of the CPU.

  parent reply	other threads:[~2003-06-10 18:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-07  1:18 [RFC] New system device API Patrick Mochel
2003-06-07 20:33 ` Pavel Machek
2003-06-09 16:19   ` Patrick Mochel
2003-06-09 18:42     ` Pavel Machek
2003-06-09 20:30       ` Patrick Mochel
2003-06-09 21:07         ` Pavel Machek
2003-06-09 21:15           ` Patrick Mochel
2003-06-09 21:23             ` Pavel Machek
2003-06-09 21:40               ` Patrick Mochel
2003-06-09 22:04                 ` Pavel Machek
2003-06-09 23:09                   ` Nigel Cunningham
2003-06-09 23:16                     ` Pavel Machek
2003-06-09 23:24                       ` Nigel Cunningham
2003-06-09 23:25                         ` Patrick Mochel
2003-06-09 23:26                         ` Pavel Machek
2003-06-09 21:32             ` Pavel Machek
2003-06-09 21:41               ` Patrick Mochel
2003-06-10 18:27               ` Jesse Pollard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-07 10:34 mikpe
2003-06-09 16:18 ` Patrick Mochel
2003-06-09 17:39 mikpe

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=03061013275402.06462@tabby \
    --to=jesse@cats-chateau.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=pavel@suse.cz \
    /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