From: Rusty Lynch <rusty@linux.co.intel.com>
To: Greg KH <greg@kroah.com>
Cc: Scott Murray <scottm@somanetworks.com>,
lkml <linux-kernel@vger.kernel.org>,
Stanley Wang <stanley.wang@linux.co.intel.com>
Subject: Re: [PATCH][2.5.59-bk]Sysfs interface for ZT5550 Redundant Host Controller
Date: 04 Feb 2003 15:19:31 -0800 [thread overview]
Message-ID: <1044400772.1114.12.camel@vmhack> (raw)
In-Reply-To: <20030204230808.GB15544@kroah.com>
On Tue, 2003-02-04 at 15:08, Greg KH wrote:
> On Tue, Feb 04, 2003 at 02:33:15PM -0800, Rusty Lynch wrote:
> > Last week I finally got access to a decent (but old) technical specification
> > for the ZT5550 redundant host controller. The document was published for
> > the ZT5550C, but I am hoping that newer versions of the RHC just add more
> > functionality to all the documented reserved bits in the document I am looking
> > at.
> >
> > The following patch adds a sysfs interface to most of the bits accessible
> > via the indirect register (through the HCINDEX and HCDATA addresses in the
> > Command and Status Register (CSR). The only bits I did not add access to
> > were the ones that are cleared by reading. There are a lot of bits to get
> > access to, which makes this patch a little bigger then I first expected,
> > so I created a new config option so only people who actually want to mess
> > with the RHC would pay for it.
> >
> > Enabling this code will cause a new directory called zt5550_rhc to be
> > created in the root of sysfs, with the following tree:
>
> Ick, don't place directories in the root of sysfs, unless you want Pat
> to come after you with a big stick.
>
> What's wrong with putting this directory either under the pci device
> that is the zt5550 (if it is a pci device), or at the least, under the
> devices/ directory.
It was just laziness. I can create a new subsystem that isn't rooted in
any other subsystem without any other information. I'll go figure out
how to root this in the zt5550 device directory.
>
> Other than that, I like your macro abuse :)
>
Yea, one thing leads to another. If wouldn't have stopped myself then
the entire file would have been implemented as one macro line.
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2003-02-04 23:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 22:33 [PATCH][2.5.59-bk]Sysfs interface for ZT5550 Redundant Host Controller Rusty Lynch
2003-02-04 23:08 ` Greg KH
2003-02-04 23:19 ` Rusty Lynch [this message]
[not found] <Pine.LNX.4.44.0302051341490.29820-100000@rancor.yyz.somanetworks.com>
2003-02-05 20:48 ` Rusty Lynch
2003-02-05 21:14 ` Scott Murray
2003-02-05 21:40 ` Rusty Lynch
2003-02-05 22:09 ` Greg KH
2003-02-05 22:20 ` Scott Murray
2003-02-06 4:12 ` Greg KH
2003-02-06 18:23 ` Rusty Lynch
2003-02-06 18:29 ` Rusty Lynch
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=1044400772.1114.12.camel@vmhack \
--to=rusty@linux.co.intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scottm@somanetworks.com \
--cc=stanley.wang@linux.co.intel.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