All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Kilian <kilian@bobodyne.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Solaris developer wants a Linux Mentor for drivers.
Date: Wed, 6 Oct 2004 14:33:25 -0700	[thread overview]
Message-ID: <20041006213325.GA25817@kroah.com> (raw)
In-Reply-To: <200410061821.i96IL9a07610@raceme.attbi.com>

On Wed, Oct 06, 2004 at 01:21:09PM -0500, Alan Kilian wrote:
> Forwarded message:
> > From: Greg KH <greg@kroah.com>
> > 
> > Why not 2.6?  No new Linux distros are shipping 2.4 kernels anymore...
> 
>   Well, I down loaded and installed RedHat-9 5 weeks ago, and it
>   is a 2.4 kernel, so I thought that would be fine.
>   (See what a novice I am?)

Heh, Red Hat 9 is quite old now (a few years old I think.)  Try the
latest Red Hat Fedora Core 2 for a more up to date distro if you like to
use Red Hat.

> > And a PCI bus driver?  
> > What kind of hardware is this?  
> > Is this a driver for a pci card, or a pci bus controller?
> 
>   This is a driver for talking to my hardware which is a PCI bus card.

So, it's a card, not a PCI bus controller, right?  That's much simpler.

>   This card has 5 large FPGAs, SRAM and dram on it which is used to
>   accelerate bioinformatics search algorithms.
> 
>   The card works under Sun Solaris and Windows/2000, and of course,
>   we would like to add Linux to the list.
> 
>   Eventually, I'll need to support DMA to and from the card, but
>   I can get by for a while just doing single-dword I/O.
> 
>   I just hacked in dev->bus->ops->read_dword(dev,1,&retval);
>   and I can read memory on the card! (Well, things don't crash anyway)

What's wrong with using readl() instead?  Use pci_read_config_dword() if
you want access to the config space.

>   If this is absolutely the wrong way to do this, please let me know!
> 
>   Note: I have no idea what the second parameter to read_dword() is!

Try getting a copy of the Linux Device Drivers book (it's also online if
you don't want to buy it) and taking a look at the pci chapter.  It
should help you out.

Do you have a pointer to your Linux driver that we might be able to help
you out with?

Good luck,

greg k-h

  reply	other threads:[~2004-10-06 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 18:21 Solaris developer wants a Linux Mentor for drivers Alan Kilian
2004-10-06 21:33 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-06 16:25 Alan Kilian
2004-10-06 17:10 ` Neil Horman
2004-10-06 17:22 ` Greg KH

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=20041006213325.GA25817@kroah.com \
    --to=greg@kroah.com \
    --cc=kilian@bobodyne.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.