From: Sven-Thorsten Dietrich <sdietrich@novell.com>
To: "Leggo, Adam (UK)" <Adam.Leggo2@baesystems.com>
Cc: linux-rt-users@vger.kernel.org, SLE-RT Development <slert-devel@suse.de>
Subject: Re: Converting a device driver for real time kernel
Date: Tue, 09 Feb 2010 01:50:22 -0800 [thread overview]
Message-ID: <1265709022.9686.14.camel@quadrophenia.thebigcorporation.com> (raw)
In-Reply-To: <B5339992F194184BABF87ECF0296990D02716BA7@GLKMS2105.GREENLNK.NET>
On Tue, 2010-02-09 at 09:32 +0000, Leggo, Adam (UK) wrote:
> Hello,
>
> What is the best way of converting an existing device driver to work
> under a real-time kernel?
>
> A device driver provided for a special serial card (Curtiss Wright SL240
> sFDFP card http://www.cwcembedded.com/products/0/1/461.html) works under
> vanilla Linux (SLES SP10 SP2 kernel 2.6.16.60-0.21-smp), but compiling
> the driver under the real time kernel (2.6.22.19-0.14-rt) the system
> locks up and crashes. The rt kernel is being used to write large amounts
> of data from the serial card to disk and testing has found the rt kernel
> has the best consistent write performance.
>
> I have gone back to the supplier and they are not interested in
> developing a real time version of the driver. So I am trying to modify
> the driver myself. The driver code can be provided if anyone wants a
> look (released under GPLv2).
>
Hi Adam,
Generally this list is focused on the mainline RT patch set, and not so
much on distro Kernels.
I might be wrong, but out-of-tree drivers probably won't get too much
TLC here either.
That being said, your version of the SLERT Kernel is quite old.
I would suggest the following:
1. first update your system and reproduce the issue
2. file a bug and attach the driver source here:
http://bugzilla.novell.com
3. Report any specific error you could capture on a serial / net
console, and provide additional details for "locks up and crashes".
Thanks,
Sven
> Any assistance would be useful.
>
> Regards,
> Adam Leggo
>
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-09 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 9:32 Converting a device driver for real time kernel Leggo, Adam (UK)
2010-02-09 9:50 ` Sven-Thorsten Dietrich [this message]
2010-02-09 11:24 ` Carsten Emde
2010-02-09 12:26 ` Luis Claudio R. Goncalves
2010-02-09 22:27 ` Thomas Gleixner
2010-02-10 12:51 ` Converting a device driver for real time kernel - OT Armin Steinhoff
2010-02-10 12:53 ` Armin Steinhoff
2010-02-10 13:05 ` uio_pci_generic not working ? Armin Steinhoff
2010-02-11 8:20 ` Armin Steinhoff
2010-02-11 10:57 ` Converting a device driver for real time kernel Leggo, Adam (UK)
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=1265709022.9686.14.camel@quadrophenia.thebigcorporation.com \
--to=sdietrich@novell.com \
--cc=Adam.Leggo2@baesystems.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=slert-devel@suse.de \
/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 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).