From a0891d42f7d5ba585e787fbf2a8a0a720ee4ff15 Mon Sep 17 00:00:00 2001 From: antrik Date: Mon, 16 Mar 2009 16:42:23 +0100 Subject: Sound support GSoC task: Rework exercise ideas Make a generic remark on what the exercise should involve. Only briefly mention porting drivers as a possible exercise task; add an alternative suggestion (random device). --- community/gsoc/project_ideas/sound.mdwn | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'community') diff --git a/community/gsoc/project_ideas/sound.mdwn b/community/gsoc/project_ideas/sound.mdwn index e22a7e19..39c4241a 100644 --- a/community/gsoc/project_ideas/sound.mdwn +++ b/community/gsoc/project_ideas/sound.mdwn @@ -33,8 +33,10 @@ in user-space is feasible. Possible mentors: ? -Exercise: Take a newer driver for a device in one of the subsystems we already -implement (disk or network) from a newer Linux version, or some other operating -system, and try to port it so that it runs in the existing driver framework. -The port needn't be elegant or complete; but it would be nice if you could get -it to work at least partially... +Exercise: This project requires kernel (driver framework) hacking as well as +some Hurd server hacking; so the exercise should involve either of these, or +even both. You could for example port some newer driver to run in the existing +framework (see the [[device_driver|driver_glue_code]] project descrption), or +try to make some fix(es) to the [unfinished random device +implementation](http://savannah.gnu.org/patch/?6088) created by Michael +Casadevall. -- cgit v1.2.3