From: Heiko Gerstung <heiko.gerstung@meinberg.de>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Backport of a 2.6.x USB driver to 2.4.32 - help needed
Date: Wed, 14 Jun 2006 15:56:05 +0200 [thread overview]
Message-ID: <44901575.8090105@meinberg.de> (raw)
In-Reply-To: <20060609162634.b98fde7c.zaitcev@redhat.com>
Hi, Pete:
Pete Zaitcev wrote:
> On Tue, 06 Jun 2006 11:48:36 +0200, Heiko Gerstung <heiko.gerstung@meinberg.de> wrote:
>
>> [...] The maintainer of the driver
>> modified a few things for me in order to address this problem ("it
>> happens because get/set_registers() are called with no process
>> context"), but he was only able to modify the 2.6.x driver for me.
>
>> I started to backport the modified version, but it seems that I ran into
>> dependency hell because I get the following two missing functions
>> reported when I try to compile the backported module:
>>
>> rtl8150.c: In Funktion »rtl8150_get_settings«:
>> rtl8150.c:790: Warnung: implicit declaration of function `in_atomic'
>> rtl8150.c: In Funktion »rtl8150_thread«:
>> rtl8150.c:857: Warnung: implicit declaration of function
>> `schedule_timeout_uninterruptible'
>
> Tell the author to do it differently. Drivers have no business
> to call in_atomic(). So, he postpones some accesses until later.
> This is an easy way out, I did it myself in 2.4's usb-serial,
> but it's wrong. I don't see what his excuse is. Mine was that
> I didn't want to debug a freaking gazillion of usb-storage
> subdrivers.
His "excuse" is that he simply has not enough time to "do it right"(tm),
he just wanted to help me with a quick workaround.
> Who's the guy, anyway? Was it Petkan? I'm sure he'll listen
> to reason, I worked with him before.
Yes, it's Petko and I know that he is a good coder and just wanted to
help me out, although he was busy with projects he gets paid for.
> I'm going to keep an eye on rtl8150 and oppose in_atomic when
> it sneaks in.
Don't worry, I was not able to resolve the problems I got by working
around other problems. We will have to check if there is another
solution for our product as we have no chance to use a 2.4 kernel anymore.
Kind regards,
Heiko
>
> -- Pete
--
------------------------------------------------------------------------
*MEINBERG Funkuhren GmbH & Co. KG*
Auf der Landwehr 22
D-31812 Bad Pyrmont, Germany
Tel.: ++49 (0)5281 9309-25
Fax: ++49 (0)5281 9309-30
eMail: heiko.gerstung@meinberg.de <mailto:heiko.gerstung@meinberg.de>
Internet: www.meinberg.de <http://www.meinberg.de/>
------------------------------------------------------------------------
Meinberg radio clocks: 25 years of accurate time worldwide
next prev parent reply other threads:[~2006-06-14 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1149588721.11795.linux-kernel2news@redhat.com>
2006-06-09 23:26 ` Backport of a 2.6.x USB driver to 2.4.32 - help needed Pete Zaitcev
2006-06-14 13:56 ` Heiko Gerstung [this message]
[not found] <6kGwd-1tt-23@gated-at.bofh.it>
[not found] ` <6kHVe-3Hs-45@gated-at.bofh.it>
2006-06-07 0:16 ` Robert Hancock
2006-06-07 6:56 ` Heiko Gerstung
2006-06-06 9:48 Heiko Gerstung
2006-06-06 11:23 ` Jesper Juhl
2006-06-06 11:41 ` Heiko Gerstung
2006-06-06 14:43 ` Lennart Sorensen
2006-06-06 14:48 ` Heiko Gerstung
2006-06-06 14:58 ` Lennart Sorensen
2006-06-06 18:30 ` Nish Aravamudan
2006-06-07 8:04 ` Jesper Juhl
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=44901575.8090105@meinberg.de \
--to=heiko.gerstung@meinberg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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