9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: da Tyga <cyberfonic@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] DigiLand DL701Q quad core tablet
Date: Fri, 19 Dec 2014 14:15:40 +1100	[thread overview]
Message-ID: <CALj3Nd3h9UO+X8wg_wLsJCNJm=YePUHSxaX=YbrCKoEdr5PvEA@mail.gmail.com> (raw)
In-Reply-To: <86r3vwiuz8.fsf@cmarib.ramside>

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

Plan9 kernel is monolithic with the drivers required for a specific
platform compiled in.

So you might need to write specific drivers for new hardware if they are
not already available.

The paper:  http://plan9.bell-labs.com/wiki/plan9/compiling_kernels/ explains
the steps required to generate a new kernel.  BTW, even for the same
hardware, the kernels are different for terminals, cpu servers, etc.


On 19 December 2014 at 07:06, <cigar562hfsp952fans@icebubble.org> wrote:
>
> cigar562hfsp952fans@icebubble.org writes:
>
> > Yes, I figured it might require some new device drivers, but why would
> > it require a new kernel?  I thought there was already a Plan 9 kernel
> > for Arm Cortex-series processors.  That's one of the reasons why I
> > developed such a crush on OMAP.  ;)
>
> BTW, that was not intended as a rhetorical question; I really am curious
> why the device would require a whole new kernel...
>
>

[-- Attachment #2: Type: text/html, Size: 1465 bytes --]

  parent reply	other threads:[~2014-12-19  3:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15 16:15 cigar562hfsp952fans
2014-11-17 14:03 ` erik quanstrom
2014-11-19 15:41   ` cigar562hfsp952fans
2014-12-18 20:06     ` cigar562hfsp952fans
2014-12-18 23:48       ` Charles Forsyth
2014-12-19  3:15       ` da Tyga [this message]
2014-12-19  7:43         ` Quintile
2014-12-19  9:33           ` Richard Miller
2014-12-19 15:14             ` Iruatã Souza

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='CALj3Nd3h9UO+X8wg_wLsJCNJm=YePUHSxaX=YbrCKoEdr5PvEA@mail.gmail.com' \
    --to=cyberfonic@gmail.com \
    --cc=9fans@9fans.net \
    /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).