From: testlaster@gmail.com (testlaster)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Linux PCI driver.
Date: Mon, 18 Aug 2014 14:30:33 +0200 [thread overview]
Message-ID: <53F1F1E9.3030003@gmail.com> (raw)
In-Reply-To: <20140818083503.GA1550@kroah.com>
Hi Greg
Yes I have read the book and some of it does make sense to me.
What doesnt make sense though is that my pci.h file that I have found
/include/linux only has like 30 lines max?
None of the functions in the book are in the header.
Thanks
Testo
On 8/18/2014 10:35 AM, Greg KH wrote:
> On Mon, Aug 18, 2014 at 09:50:44AM +0200, testlaster wrote:
>> Hey Guys
>>
>> Im writing a PCI driver in Linux ( Lubuntu ). Now its not an entire
>> driver its really just a little program that will latch onto a space of
>> ram and dump the entire content of the ram into a file.
>> I have done this before in a Unix/Linux based OS and it took me quite a
>> while to figure it out.
>>
>> So at startup the configuration for the PCI is already done so I wont
>> have to do any of that myself.
>> I really just need to set a pointer to a register.
>>
>> My problem is that I cant find the functions to do that for linux.
>> I cant find similar functions to things like :
>> PCI_ATTACH()
>> pci_attach_device();
>> mmap_device_memory();
>>
>> I think that is really all I need at the moment.
>> Anybody have some ideas of where I can start looking?
> Have you read the book, Linux Device Drivers, 3rd edition, it's free
> online and has a whole chapter on PCI that should answer these questions
> for you.
>
> If not, please feel free to post your code and we will be glad to review
> it.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2014-08-18 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 7:50 Linux PCI driver testlaster
2014-08-18 8:35 ` Greg KH
2014-08-18 12:30 ` testlaster [this message]
2014-08-18 12:33 ` Greg KH
2014-08-18 13:06 ` testlaster
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=53F1F1E9.3030003@gmail.com \
--to=testlaster@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).