Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Driver HOWTO ?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Armin Steinhoff  
View profile  
 More options Nov 8 2005, 2:34 pm
Newsgroups: comp.os.minix
From: Armin Steinhoff <a-steinh...@web.de>
Date: Tue, 08 Nov 2005 20:34:10 +0100
Local: Tues, Nov 8 2005 2:34 pm
Subject: Re: Driver HOWTO ?

jfath...@aol.com wrote:
> Armin Steinhoff wrote:

>>AFAIS ... it should be very easy to port our QNX4 based
>>fieldbus drivers to Minix 3 :)

> My enthusiasm for Minix 3 derives from my own QNX 4 (POSIX microkernel)
> experience several years ago.  Minix 3 will need to catch on and
> develop a user community beyond the classroom to approach QNX in
> utility, but if it does, it could become a really compelling
> alternative.

It depends on your requirements. If you don't need real-time and
threads, but a robust and secure micro kernel running on a single
CPU ... Minix 3.0 could be an alternative.

However ... Minix 3.0 is new and QNX is now ~20 years in the RTOS
market, so you have to be realistic :)

> Please note that I have no dispute with QNX.  They make a very fine
> operating system and I enjoyed using it.  I just want an open source
> alternative so I can master the internals (the technical appeal), and
> avoid licensing fees (the commercial appeal).

> Segin wrote:

>>Is this driver of yours comercially developed? And if so,
>>will the Minix version be under a OSI-approved license?

> Since Minix 3 is released under a BSD style license, there is no
> requirement that Armin's driver be released under an OSI approved
> license.  This is the chief non-technical appeal of Minix 3.

> If someone develops generally useful code that runs under Minix 3, they
> should contribute that back to the community since they benefit from
> the generous contributions of others.  But if their value add targets a
> very narrow market where their source would only be of value to their
> direct commercial competitors, they should be free to hold that source
> closed.

> Viral licensing such as the GPL is often a problem for commercial
> developers in niche markets who would otherwise like to develop for
> Linux.  It is great that Minix 3 went with a BSD style license to avoid
> this problem.

Drivers for Minix 3.0 are not kernel modules ... so 'tainted drivers' is
not an issue for Minix 3.0. It is a real big problem with LINUX 2.x ...
as the recent discussion about a kernel driver API for LINUX shows.

LINUX is on the way to loose support for high tech hardware ... graphic
controller a.s.o.

> The ability to hold source closed where warranted should encourage
> Minix 3 adoption, so users who select this path should be respected.
> They contribute in a useful, albeit less direct, manner.

Yes ... the contribution could be to open the doors for new areas of
applications of Minix 3.0.

Regards

--Armin

> Thanks.

> Jim


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.