linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Armin Steinhoff <as@steinhoff-automation.com>
To: linux-rt-users@vger.kernel.org
Subject: Re: Converting a device driver for real time kernel - OT
Date: Wed, 10 Feb 2010 13:53:33 +0100	[thread overview]
Message-ID: <4B72AC4D.2060900@steinhoff-automation.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1002092317420.2811@localhost.localdomain>


Hi all,

I know it's OT ... but what is the real name of

 - "real time kernel (2.6.22.19-0.14-rt)"
 - "!RT kernel" 
 - "-rt kernel"

Any ideas ?  Is it the RTP kernel --- P stands for pre-emption ?

--Armin





Thomas Gleixner wrote:
> On Tue, 9 Feb 2010, 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).
>>  
>> Any assistance would be useful.
>>     
>
> The problem of the driver is probably broken locking, which needs to
> be fixed for !RT as well.
>
> But if you want to fix it your self and need some assistance it would
> be helpful if you could:
>
> 1) Run against a recent -rt kernel
>
> 2) provide a serial console log of the kernel crash
>
> 3) run the kernel with CONFIG_PROVE_LOCKING=y and provide the output
>
> 4) upload the source to some place so we can at least have a look at
>    the code to give you hints.
>
> Thanks,
>
> 	tglx
>
> --
> 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
>
>   


  parent reply	other threads:[~2010-02-10 12:52 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
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 [this message]
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=4B72AC4D.2060900@steinhoff-automation.com \
    --to=as@steinhoff-automation.com \
    --cc=linux-rt-users@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 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).