From: Christoph Hellwig <hch@infradead.org>
To: Mirko Lindner <mlindner@syskonnect.de>
Cc: Stephen Hemminger <shemminger@osdl.org>,
Jeff Garzik <jgarzik@pobox.com>,
Mirko Lindner <demon@pro-linux.de>,
netdev@oss.sgi.com, Ralph Roesler <rroesler@syskonnect.de>
Subject: Re: [PATCH] (4/25) sk98: change #define to typedef
Date: Wed, 17 Nov 2004 15:01:34 +0000 [thread overview]
Message-ID: <20041117150133.GA8874@infradead.org> (raw)
In-Reply-To: <419A231F.4020104@syskonnect.de>
> Note that the kernel BSD sk driver was _not_ written by SysKonnect and
> only supports Genesis and Yukon1; linux supports Genesis (single and
> dual), Yukon1, Yukon Plus, Yukon EC, Yukon FE and Yukon2 (single and
> dual).
They have Yukon2 support for while - unlike Linux.
> The BSD sk driver supports substantially less functionality than
> the Linux driver. For example, there is no link failover capability in
> the sk driver;
Which isn't something that belongs into a driver anyway. It also
means you common code is obsfucated enough that no one noticed :)
> For instance the symbol SK_IOC mentioned in your mail:
>
> > -#define SK_IOC char __iomem *
> > +typedef void __iomem *SK_IOC;
>
> is used in a large number of OS independent driver files (e.g. skvpd.c).
> The -for instance- file skvpd.c used by our Linux driver is used
> at the same time without any changes by all our other drivers running
> on other operating systems (e.g. Solaris, Windows).
>
> This is the reason why we need to redefine this symbol to the Linux
> specific implementation (void __iomem).
And you still haven't explained why your common code uses such
a broken structure instead of having some semi-opaque private data
passed around everywhere.
Also note that we don't new drivers using such horrible "common code"
anymore, you can be happy you sneaked it in at all a few years ago.
next prev parent reply other threads:[~2004-11-17 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 15:56 [PATCH] (4/25) sk98: change #define to typedef Mirko Lindner
2004-11-16 17:12 ` Stephen Hemminger
2004-11-17 15:01 ` Christoph Hellwig [this message]
2004-11-19 0:23 ` Stephen Hemminger
[not found] <20041115150910.0f3b8498@zqx3.pdx.osdl.net>
2004-11-15 23:22 ` Stephen Hemminger
2004-11-16 8:22 ` Christoph Hellwig
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=20041117150133.GA8874@infradead.org \
--to=hch@infradead.org \
--cc=demon@pro-linux.de \
--cc=jgarzik@pobox.com \
--cc=mlindner@syskonnect.de \
--cc=netdev@oss.sgi.com \
--cc=rroesler@syskonnect.de \
--cc=shemminger@osdl.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).