From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from imz.re ([94.23.91.129]) by ur; Mon Oct 12 16:02:30 EDT 2015
Received: from [192.168.90.11] (77-252-177-208.static.ip.netia.com.pl [77.252.177.208])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by imz.re (Postfix) with ESMTPSA id 59C4880D48;
	Mon, 12 Oct 2015 22:02:28 +0200 (CEST)
Message-ID: <561C11D2.5060301@imz.re>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: optimized compliant SSL hardware self-signing framework
Date: Mon, 12 Oct 2015 22:02:26 +0200
From: ghi <ghi@imz.re>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: cinap_lenrek@felloff.net
CC: 9front@9front.org
Subject: Re: [9front] Audio in Lenovo T400
References: <0b109d174515546318e7979e0615ae3d@felloff.net>
In-Reply-To: <0b109d174515546318e7979e0615ae3d@felloff.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

> plan9 kernel is quite simple, you should have no problem figuring
> it out by looking at the other drivers. the kernel you build is
> build from a configuration file, /sys/src/9/pc/9pcf is build from
> /sys/src/9/pc/pcf for example. this file contains the list of
> drivers that get build into it. there are two types of kernel
> drivers:
>
> dev: which export a Dev structure with function pointers to
> implement a (kernel) fileserver, they are all named dev*.c.
>
> link: which just export a <nameofdriver>link() function
> that gets called early on boot. the audio and ethernet drivers are
> of this kind. they do not implement the device fileservice directly
> but just register themselfs in ther link function with a dev.
>
> you build a kernel with mk. mk 'CONF=confname' to build a kernel
> of a specific configuration. gives you 9confname kernel image.
Thank you for explaining that. The Plan 9 has again charmed me with it's 
simplicity.

BR
ghi