9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* Re: [9fans] Crazy idea... or a new project?
@ 2000-11-24 19:05 rob pike
  2000-11-24 21:06 ` Francisco J Ballesteros
  0 siblings, 1 reply; 24+ messages in thread
From: rob pike @ 2000-11-24 19:05 UTC (permalink / raw)
  To: 9fans

> Another way could be to be able to link the kernel
> with device drivers before loading it, and keep
> the kernel just with devices used. I think that
> could be done by making each driver provide a
> (user) program to check if the device is there,
> and linking a second kernel depending on what's
> there. 

You don't have a user program running when you're trying
to boot the kernel.

-rob



^ permalink raw reply	[flat|nested] 24+ messages in thread
* Re: [9fans] Crazy idea... or a new project?
@ 2000-11-27  2:36 okamoto
  2000-11-27  6:16 ` Boyd Roberts
  0 siblings, 1 reply; 24+ messages in thread
From: okamoto @ 2000-11-27  2:36 UTC (permalink / raw)
  To: 9fans

nclude: /mail/fs/mbox/41/raw

>Yup. Everyone knows the right answer is to combine
>p-n-p with n-p-n.

I rather love to listen music from oldest glass tubes.  :-)

Kenji



^ permalink raw reply	[flat|nested] 24+ messages in thread
* Re: [9fans] Crazy idea... or a new project?
@ 2000-11-24 23:47 rob pike
  2000-11-24 23:52 ` Boyd Roberts
  2000-11-25 18:52 ` Fariborz 'Skip' Tavakkolian
  0 siblings, 2 replies; 24+ messages in thread
From: rob pike @ 2000-11-24 23:47 UTC (permalink / raw)
  To: 9fans

Yup. Everyone knows the right answer is to combine
p-n-p with n-p-n.

-rob



^ permalink raw reply	[flat|nested] 24+ messages in thread
* Re: [9fans] Crazy idea... or a new project?
@ 2000-11-24 22:40 presotto
  0 siblings, 0 replies; 24+ messages in thread
From: presotto @ 2000-11-24 22:40 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

I seem to be missing messages from this stream so
excuse me if this has already been suggested:

I guess it depends on what problem you are trying to
solve.  We have lots (> 100) of systems that boot off
of LAN's.  We end up with kernels stuffed full of
drivers because otherwise, we'ld have to keep a database
lying around somewhere for each system and spend time
making lots of kernels each time we change something.
Granted we could write enough software to make this
painless, but it's one more thing to screw up.

I was actually fond of an idea I've heard from Rob or
Ken, can't remember which.  To address the problem, he
suggested the dhcp daemon link the kernel on the fly.
It could use a hardware vector passed in the dhcp request
(generated from plan9.ini perhaps) and return the file
name of the result so that the system could tftp it over.

Unfortunately, I find this all a lot less of a problem than
figuring out what IRQ's and IO ports to assign devices or that
of getting a new VGA board working.

[-- Attachment #2: Type: message/rfc822, Size: 2314 bytes --]

From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Crazy idea... or a new project?
Date: Fri, 24 Nov 2000 23:24:09 +0100
Message-ID: <01e701c05665$44417500$0ab9c6d4@cybercable.fr>

From: Scott Schwartz <schwartz@bio.cse.psu.edu>

> Just to digress for a moment, I've never liked the idea of loadable
> device drivers, because they seeem like such a stopgap measure.

maybe you could 'plumb' them.  after boot the kernel gets
handed up a file with rules/whatever to load device drivers
based on interrupts or other device ready 'events'.

i was thinking about digital uda-50 interfaces.  you could
just plug 'em in and ultrix would autoconf them at run
(ie. any) time.  of course, the driver was already loaded.

probably hard to generalise, but it might work out.


^ permalink raw reply	[flat|nested] 24+ messages in thread
* Re: [9fans] Crazy idea... or a new project?
@ 2000-11-24 22:16 rob pike
  0 siblings, 0 replies; 24+ messages in thread
From: rob pike @ 2000-11-24 22:16 UTC (permalink / raw)
  To: 9fans

Having the window system allocate memory from unpageable ram bothers me too,
and is surely fixable, but putting pixels in user space with user code pumping them
had worse problems.  The last pieces of this design space have not been explored.

-rob



^ permalink raw reply	[flat|nested] 24+ messages in thread
* Re: [9fans] Crazy idea... or a new project?
@ 2000-11-24  8:37 nemo
  0 siblings, 0 replies; 24+ messages in thread
From: nemo @ 2000-11-24  8:37 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

Another way could be to be able to link the kernel
with device drivers before loading it, and keep
the kernel just with devices used. I think that
could be done by making each driver provide a
(user) program to check if the device is there,
and linking a second kernel depending on what's
there. 



[-- Attachment #2: Type: message/rfc822, Size: 4114 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 580 bytes --]

That's a little simplistic.  The x86 is a lousy architecture,
and you're right about the compilers etc.  But all those
lousy drivers, VGAs, USB floppies, it goes on and on.
Are any two the same?  I doubt it.  That's the horror of
PCs, yet is a perhaps unavoidable consequence of the
history that made the PC dominant (c.f. the Mac).

The PC kernel for Plan 9 is huge because of all the drivers
it must have to run on all devices.  Sure we could have
(and perhaps should have) loadable device drivers,
but that is a solution to a problem that shouldn't exist.

-rob


[-- Attachment #2.1.2: Type: message/rfc822, Size: 1463 bytes --]

From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Crazy idea... or a new project?
Date: Thu, 23 Nov 2000 19:05:08 -0500
Message-ID: <20001124000509.EF643199EE@mail.cse.psu.edu>

I don't agree about the x86.
Sure it's an ugly chip.
Sure it and its PC hosts are complicated.
But the bootstrap code and the compiler
are written.  In Plan 9, it's no different
to write applications for the x86 than it
is to write them for any other architecture.

Russ

^ permalink raw reply	[flat|nested] 24+ messages in thread
[parent not found: <rob@plan9.bell-labs.com>]
* Re: [9fans] Crazy idea... or a new project?
@ 2000-11-24  0:05 Russ Cox
  2000-11-24  0:08 ` Boyd Roberts
  0 siblings, 1 reply; 24+ messages in thread
From: Russ Cox @ 2000-11-24  0:05 UTC (permalink / raw)
  To: 9fans

I don't agree about the x86.
Sure it's an ugly chip.
Sure it and its PC hosts are complicated.
But the bootstrap code and the compiler
are written.  In Plan 9, it's no different
to write applications for the x86 than it
is to write them for any other architecture.

Russ


^ permalink raw reply	[flat|nested] 24+ messages in thread
* [9fans] Crazy idea... or a new project?
@ 2000-11-23 13:25 Andrew Zubinski
  2000-11-23 22:51 ` Richard
  2000-11-23 22:55 ` Boyd Roberts
  0 siblings, 2 replies; 24+ messages in thread
From: Andrew Zubinski @ 2000-11-23 13:25 UTC (permalink / raw)
  To: 9fans

I think that I'm correct in next sentences:

1. Plan9 support community (both developers and users) is small
2. Any OS (even so beautifull like Plan9) whithout x86 platform support
is dead OS
3. x86 platform is evil for small community
4. Because small community must support all spectre of PC-compatible
garbage
5. So, there are no free time to develop application software
6. And without application software even great OS will be no more than
"very
interesting thing" for very small community

IMHO, there is only one way to realize all Plan9 power - new hardware
platform:
low-cost, open at specifications level, non-x86.
Why it must be open and cheap?
Are you remember the stories of NeXT and Be?

Let it be wearable Plan9 terminal especially designed with requirements
of small
electronics companies in mind (simple and small PCB, chips with small
pin-outs). And for a CPU & file servers we must create portable and
POSIX-OS-independent implementations (it is hard but possible).

As engineer I see the prototype of such "Plan9Wear":
------------------
System CPU - low-cost ($25-30 in sample quantity) MIPS-clone
(with frequency about 100-133 MHz and power ~1-3 W)
like IDT R/RC4640 or NEC). And we have the MIPS kernel...
------------------
System DSP - for the bitblt implementation, speech controls (why not?)
and etc.
------------------
System Bus Controller - FPGA based or low-cost single chip
PCI bridge (DRAM controller)
------------------
System Memory - 128 MB standard DIMM + Flash BOOT
------------------
Interfaces - USB 2.0 + IEEE-802.11a high-speed wireless
------------------
Grayscale microdisplay (Kopin 1280x1024, 256 gray levels), $100-150
(???)

IMHO, the wearable Plan9 will be really great thing. And main system
ideas are very
suitable for wireless and wearable applications.

Maybe it is time to start development ????

P.S.
Sorry for my ugly English... :-)


^ permalink raw reply	[flat|nested] 24+ messages in thread

end of thread, other threads:[~2000-11-27  8:21 UTC | newest]

Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-11-24 19:05 [9fans] Crazy idea... or a new project? rob pike
2000-11-24 21:06 ` Francisco J Ballesteros
2000-11-24 21:28   ` Boyd Roberts
2000-11-24 23:37     ` Francisco J Ballesteros
2000-11-24 23:40       ` Boyd Roberts
2000-11-25  1:57         ` Francisco J Ballesteros
  -- strict thread matches above, loose matches on Subject: below --
2000-11-27  2:36 okamoto
2000-11-27  6:16 ` Boyd Roberts
2000-11-27  8:21   ` Andy Newman
2000-11-24 23:47 rob pike
2000-11-24 23:52 ` Boyd Roberts
2000-11-25 18:52 ` Fariborz 'Skip' Tavakkolian
2000-11-24 22:40 presotto
2000-11-24 22:16 rob pike
2000-11-24  8:37 nemo
     [not found] <rob@plan9.bell-labs.com>
2000-11-24  0:41 ` rob pike
2000-11-24  0:48   ` Boyd Roberts
2000-11-24 22:13   ` Scott Schwartz
2000-11-24 22:24     ` Boyd Roberts
2000-11-24  0:05 Russ Cox
2000-11-24  0:08 ` Boyd Roberts
2000-11-23 13:25 Andrew Zubinski
2000-11-23 22:51 ` Richard
2000-11-23 22:55 ` Boyd Roberts

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).