All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-pci@vger.kernel.org
Subject: Re: PCI card not accessible; I/O ports at <ignored>
Date: Wed, 18 Jan 2012 21:03:25 +0100	[thread overview]
Message-ID: <2291613.bPZ67F62Nj@eto> (raw)
In-Reply-To: <4F170DDB.3010105@meinberg.de>

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

Am Mittwoch 18 Januar 2012, 19:22:19 schrieben Sie:
> Greg KH wrote:
> > On Wed, Jan 18, 2012 at 04:49:27PM +0100, Martin Burnicki wrote:
> >> Hi folks,
> >> 
> >> I'm maintaining the driver software for the PCI cards manufactured
> >> by our company, Meinberg Funkuhren in Germany. Basically our Linux
> >> driver supports all our PCI cards on all Linux kernels 2.6.x and
> >> 3.x. The PCI cards are e.g. GPS receivers, radio clocks, or IRIG
> >> time code receivers.
> > 
> > Nice, any reason why these drivers aren't in the main kernel.org tree?
> 
> Yes, you wouldn't like the coding style of our driver ;-)
> 
> Seriously, I have discussed this with some Linux guys before, and also
> with some folks from *BSD who also wanted to pick up the driver into
> their *BSD source trees.

I've had such a driver before. Trust me, it was a great relief once I got rid 
of it because I did not have to maintain the os abstraction layer anymore. And 
many of the lower level functions you need to do by hand for all systems can 
be done with fewer calls on nearly all systems. Just the borders of these 
calls differ between the systems, so you can't abstract this away in the 
wrapper layer.

And noone stops you to have your driver available for older kernel releases 
too. But plugging something in and it just works is just cool ;)

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-01-18 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 15:49 PCI card not accessible; I/O ports at <ignored> Martin Burnicki
2012-01-18 16:28 ` Greg KH
2012-01-18 18:22   ` Martin Burnicki
2012-01-18 20:03     ` Rolf Eike Beer [this message]
2012-01-18 20:35     ` Greg KH
2012-01-19  9:43       ` Martin Burnicki
2012-01-18 17:16 ` Bjorn Helgaas
2012-01-18 18:27   ` Martin Burnicki
2012-01-19 11:34   ` Martin Burnicki

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=2291613.bPZ67F62Nj@eto \
    --to=eike-kernel@sf-tec.de \
    --cc=linux-pci@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.