From: NZG <ngustavson@emacinc.com>
To: comedi@comedi.org
Cc: Ian Abbott <abbotti@mev.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6VMM, uClinux, & Comedi
Date: Tue, 2 Aug 2005 16:12:15 -0500 [thread overview]
Message-ID: <200508021612.15183.ngustavson@emacinc.com> (raw)
In-Reply-To: <42EF74C1.6020909@mev.co.uk>
I'm running comedi-0.7.70, but the issue is seems be be coming from the fact
that I'm using a nommu arch.
grepping through my arch and include/asm, these symbols are indeed not
defined.
This makes sense because uClinux has no true virtual memory, vmalloc is just a
wrapper for kmalloc.
The implementation of these functions is probably trivial, but It's taking me
a bit since I didn't really understand the VM code before (now I have a small
inkling)
I'll get there, I'm just surprised this hasn't been attempted before.
NZG.
On Tuesday 02 August 2005 08:27, Ian Abbott wrote:
> On 01/08/05 14:17, NZG wrote:
> > I managed to successfully cross-compile Comedi for the Coldfire uClinux
> > 2.6, however it has several unresolved symbols when I try to load it.
> >
> > comedi: Unknown symbol pgd_offset_k
> > comedi: Unknown symbol pmd_none
> > comedi: Unknown symbol remap_page_range
> > comedi: Unknown symbol pte_present
> > comedi: Unknown symbol pte_offset_kernel
> > comedi: Unknown symbol VMALLOC_VMADDR
> > comedi: Unknown symbol pte_page
>
> It's probably coming to grief in Comedi's Linux compatibility headers
> somewhere, but as this stuff has changed a few times, which version of
> Comedi and which kernel version are you using exactly?
next prev parent reply other threads:[~2005-08-02 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 13:17 2.6VMM, uClinux, & Comedi NZG
2005-08-01 15:18 ` Bernd Porr
2005-08-02 13:27 ` Ian Abbott
2005-08-02 21:12 ` NZG [this message]
2005-08-03 10:03 ` Ian Abbott
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=200508021612.15183.ngustavson@emacinc.com \
--to=ngustavson@emacinc.com \
--cc=abbotti@mev.co.uk \
--cc=comedi@comedi.org \
--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