LKML Archive on
help / color / mirror / Atom feed
From: Mark Gross <>
To: Christoph Hellwig <>, Tim Bird <>
Cc: linux kernel <>
Subject: Re: ANNOUNCE: CE Linux Forum - Specification V1.0 draft
Date: Mon, 17 May 2004 13:42:49 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Monday 17 May 2004 12:19, Christoph Hellwig wrote:
> On Mon, May 17, 2004 at 12:05:36PM -0700, Tim Bird wrote:
> > I am writing to announce the availability of the first draft of
> > the CE Linux Forum's first specification.  This specification
> > represents the efforts of six different technical working groups
> > over about the last 9 months.
> If you want my 2Cent:
>  - stop these rather useless specifications and provide patchkits instead
>  - try to actually submit the patches upstream to get a feeling which
>    of your 'features' are compltely hopeless, which are okay and which
>    can better be solved in different ways.

All that these "organizations" are doing is collecting REAL requirements for 
features that REAL application developers need.  As well as putting up 
resources to enable the features.

These features represent input from real application developers and system 
integrators on requirements that would be cool for their applications if 
Linux supported them.  Why not look at them from the "what features are 
missing from Linux today and by whom" point of view?

It is also true that most of the requirements exist only if there is some type 
of implementation available.  As such patches for many of the components of 
such specifications are by definition already available at the time of the 
announcement.  (most may need significant work to bring up to date with the 
current kenrel tree, but they do exist)  

The patches do get submitted on a regular basis to the LKML.  Many seem to get 
ignored.  Some of them should, but it seems to me that if features keep 
coming up as requirements in such "specifications" and resources continue to 
work on the feature, then there must be some real need for it.  

BTW, Has anyone actually looked at the latest high res timer patch for 2.6.5?  
I has a new design for the sub-jiffies timer interrupt source.  

It provides an implementation of a the missing feature of low jitter (< 1ms), 
system wide time base via a standard API. ( POSIX would be nice)  

My opinions are my own and not that of my employer, duh.


  parent reply	other threads:[~2004-05-17 20:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 19:05 Tim Bird
2004-05-17 19:19 ` Christoph Hellwig
2004-05-17 19:59   ` Tim Bird
2004-05-17 20:42   ` Mark Gross [this message]
2004-05-17 20:48     ` Arjan van de Ven
     [not found]     ` <>
2004-05-18 19:32       ` Mark Gross
2004-05-18 19:56         ` Russell King
2004-05-18 20:45           ` Bartlomiej Zolnierkiewicz
2004-05-18 20:00         ` viro
2004-05-19 19:30       ` Tim Bird
2004-05-19 21:57         ` Russell King
2004-05-19 22:02           ` Jeff Garzik
2004-05-19 23:46           ` Tim Bird
2004-05-19 22:08         ` Theodore Ts'o
2004-05-19 23:37           ` Tim Bird
2004-05-17 21:22   ` Tim Bird
2004-05-19 15:27     ` Adrian Bunk
2004-05-19 16:59       ` Tim Bird
2004-05-19 20:16         ` Adrian Bunk
2004-05-19 20:38           ` Tim Bird
2004-05-19 20:48             ` Nicolas Pitre
2004-05-19 22:00         ` Russell King

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: ANNOUNCE: CE Linux Forum - Specification V1.0 draft' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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