public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kilian@bobodyne.com (Alan Kilian)
To: linux-kernel@vger.kernel.org
Subject: Solaris developer wants a Linux Mentor for drivers.
Date: Wed, 6 Oct 2004 11:25:31 -0500 (CDT)	[thread overview]
Message-ID: <200410061625.i96GPVu01974@raceme.attbi.com> (raw)



  Kernel folks,

    I am in the process of porting a Sun Solaris PCI bus driver
    that I wrote over to a 2.4 kernel, and I could use a mentor
    just to get me over the initial bumps.

    I have a module that can be loaded, and detects my card, and
    responds to ioctl() calls properly, so I'm moving right along,
    but I do have some problems now.

    1) If I "oops" in my module, I cannot unload it with:
       # /sbin/rmmod sse    
       sse: Device or resource busy

       I have only figured out that a reboot cleans things up again.

    2) An example of using pci_ops read_dword() would be superb.

    By the way, this development environment is really slick
    compared to Solaris. When I "oops" in Solaris, the kernel
    panics and I'm in for a messy fsck on the way back up. This
    is a great improvement.

    Thanks in advance for any help any of you may provide.

    After this, there will be one more Linux PCI bus driver developer
    in the world, and that can't be a bad thing.

                          -Alan

-- 
- Alan Kilian <kilian(at)timelogic.com> 
Director of Bioinformatics, TimeLogic Corporation 763-449-7622

             reply	other threads:[~2004-10-06 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 16:25 Alan Kilian [this message]
2004-10-06 17:10 ` Solaris developer wants a Linux Mentor for drivers Neil Horman
2004-10-06 17:22 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2004-10-06 18:21 Alan Kilian
2004-10-06 21:33 ` 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=200410061625.i96GPVu01974@raceme.attbi.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox