mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David VomLehn <dvomlehn@cisco.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Jamie Lokier <jamie@shareable.org>, Ingo Molnar <mingo@elte.hu>,
	Arjan van de Ven <arjan@infradead.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux USB Mailing List <linux-usb@vger.kernel.org>,
	Linux Embedded Mailing List <linux-embedded@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Wait for console to become available, v3.2
Date: Wed, 22 Apr 2009 22:08:53 +0100	[thread overview]
Message-ID: <20090422220853.0af12ece@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090422205427.GA28435@cuplxvomd02.corp.sa.net>

> Alright, I know you (Alan (Stern)) know about USB. I think someone else
> mentioned Firewire. What other hotpluggable buses do we need to worry about
> and how can we get them interested?

In theory any console can be hot pluggable - PCI-X hotplug video cards,
hotplug serial ports. In fact right now bad things occur if you
hot-unplug consoles.

> 2.	All devices have been probed
> If we exit for reason 2, it means that no such device is present,
> and we go on to the do the appropriate thing for that device class.

USB has no notion of #2 really

> Yes, I think we absolutely exclude devices plugged in after boot. I think such
> usage, if it needs to be supported, can be handled with hot plugging. I'm a
> little squishy on whether we might to be able to hot plug USB consoles as I
> have a request to support this, but I think it's a separate issue from
> supporting hot pluggable boot devices and I'm not worrying about it now.

This still assumes you can tell the difference, but USB in particular is
rather like undergraduate students - they turn up when they feel like it
at some point after they get kicked into life.

I don't think that is a big problem because our bus model is basically
that all devices are discovered asynchronously (increasingly so with
Arjan's speed up patches). A console model therefore has to deal with
console addition and removal being dynamic.

  reply	other threads:[~2009-04-22 21:10 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 23:40 David VomLehn
2009-04-21  6:43 ` Ingo Molnar
2009-04-21  7:13   ` David Brownell
2009-04-21  8:03     ` Ingo Molnar
2009-04-21 17:11     ` David Woodhouse
2009-04-21 17:29       ` David VomLehn
2009-04-21 17:37         ` Linus Torvalds
2009-04-21 17:59           ` David VomLehn
2009-04-21 17:41         ` David Woodhouse
2009-04-21 17:31       ` Linus Torvalds
2009-04-21 19:25         ` Alan Cox
2009-04-21 23:17           ` David VomLehn
2009-04-22  8:25         ` Jamie Lokier
2009-04-22  9:11           ` Alan Cox
2009-04-22 10:39             ` Jamie Lokier
2009-04-21 13:35   ` Arjan van de Ven
2009-04-21 13:50     ` Ingo Molnar
2009-04-21 14:05       ` Jamie Lokier
2009-04-21 14:26         ` Ingo Molnar
2009-04-21 14:37           ` Alan Cox
2009-04-22  8:22             ` Jamie Lokier
2009-04-22  9:13               ` Alan Cox
2009-04-21 16:42           ` David VomLehn
2009-04-21 14:36         ` Alan Stern
2009-04-21 16:52           ` David VomLehn
2009-04-21 19:09             ` Alan Stern
2009-04-21 23:08               ` David VomLehn
2009-04-22 15:40                 ` Alan Stern
2009-04-22 20:54                   ` David VomLehn
2009-04-22 21:08                     ` Alan Cox [this message]
2009-04-22 21:24                       ` Alan Stern
2009-04-24  0:35                         ` David VomLehn
2009-04-24 19:20                           ` Alan Stern
2009-04-24 21:32                             ` David VomLehn
2009-04-24 22:19                               ` Jamie Lokier
2009-04-24 23:10                                 ` David VomLehn
2009-04-25  1:41                                   ` Jamie Lokier
2009-04-25  3:11                                     ` Alan Stern
2009-04-26 19:52                                       ` Jamie Lokier
2009-04-26 21:20                                         ` Alan Stern
2009-04-26 21:37                                           ` Jamie Lokier
2009-04-26 22:36                                             ` Kay Sievers
2009-04-26 23:12                                               ` Jamie Lokier
2009-04-26 23:23                                                 ` Kay Sievers
2009-04-26 23:46                                                   ` Jamie Lokier
2009-04-26 17:55                                     ` David VomLehn
2009-04-22  5:35               ` David VomLehn

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=20090422220853.0af12ece@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=dvomlehn@cisco.com \
    --cc=hpa@zytor.com \
    --cc=jamie@shareable.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stern@rowland.harvard.edu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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®