From: testlaster@gmail.com (testlaster)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Writing makefiles for headers outside 'usr/include'
Date: Tue, 26 Aug 2014 11:09:23 +0200 [thread overview]
Message-ID: <53FC4EC3.3050709@gmail.com> (raw)
In-Reply-To: <CAE4k238Q5_cPPptDcC+16xP3t+Pt_iGOzM8D6xRXcCSKRpUxKA@mail.gmail.com>
Alright soo I want to access a piece of allocated memory through the PCI
device which is PLX9054 chip.
All I really need to do is gain access to it and dump the data from it
into a file.
Now the user space one would have been nice if I could use it but the
PCI.H in user space dev folder " /usr/include " is really limiting
OR I just dont know how I can do it with only the 8 or so functions
given to me there. Also I think permissions might be a problem in user
space.
Because as far as I know accessing a PCI devices Memory you need to
populate a struct with and give it a handle and then pass it on to
mmap() if im not mistaken.
But I cant even get to try and code it cause at the moment I cant even
seem to get the environment/makefiles set up correctly to be able to
link all of the needed .H
files and libraries in.
On 8/26/2014 10:31 AM, Anders Darander wrote:
> On 26 August 2014 10:09, testlaster <testlaster@gmail.com> wrote:
>> So the initial problem I'm having is that wanting to use headers and their
>> libs like module.h and init.d and pci.h for instance can't be used by simply
>> going #include <pci.h> because if you check the actual pci.h (40 lines or
>> so) file you will find that its allot shorter then the usual dev pci.h so
>> needless to say you can't use all the functions. So now I have to use
>> makefiles to point to other directories.
> Stop for a moment.
> What are you trying to do? Are you writing a kernel module or a user-space
> application?
>
>> I've been trying to create makefiles but at the moment the errors just rack
>> up so much that I really don't know what part of the process is at fault. Is
>> it the C or the headers or the wrong libraries? I'm kind of clueless to
>> where the libraries might even be.
>>
>> Could someone please help me write a makefile for Linux headers and their
>> libraries that is not in the usual /usr/include directory? The source files
>> that I want to use will be in
>> usr/src/linux-headers-3.13.0.32-generic/include. Also if they are in the
>> makefile how will I include them in the source?
> If you're writing a kernel module, you can't use the headers from /usr/include.
>
> If you're writing a user-space application, yuo should use the headers from
> /usr/include, not the one from /usr/src/linux-headers-3.13.0.32-generic/include.
>
> Let us know what you're trying to do, what you've got sofar, and what errors
> you're getting.
>
> Cheers,
> Anders
>
prev parent reply other threads:[~2014-08-26 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 8:09 Writing makefiles for headers outside 'usr/include' testlaster
2014-08-26 8:31 ` Anders Darander
2014-08-26 9:09 ` testlaster [this message]
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=53FC4EC3.3050709@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).