On Tue, Apr 15, 2008 at 12:38 PM, Paul Romero [EMAIL PROTECTED] wrote:
Is there loadable driver support--insmod etc., for the M5249C3 ?
If so, where can one find relevant instructions ? Also, I am
using the 2.4.x kernel and version 2.4.27 of UC Linux.
Busybox includes module utilities like
On Mon, Mar 31, 2008 at 8:59 PM, David van Geest
[EMAIL PROTECTED] wrote:
FATAL: /home/rr/uCLinux/uClinux-dist/user/modTest/modTest.o has no symtab?
Problem solved - turns out make was using the wrong compiler. I fixed
it by adding the ARCH and CROSS_COMPILE flags to the makefile like so
Hi all,
I'm trying to compile a Hello World loadable kernel module for 2.6,
but am failing at the MODPOST stage. The ultimate end is to get an
Edge Port Module LKM working for the MCF5275, but that's somewhat
irrelevant right now.
From the make output, it would appear that MODPOST can't find
On Mon, Mar 31, 2008 at 9:17 PM, Robert P. J. Day [EMAIL PROTECTED] wrote:
http://www.crashcourse.ca/wiki/index.php/Writing_your_first_kernel_module
Robert, thanks for the link. However, it doesn't really address my
problem. Your hi.c and Makefile actually get me less far than my own
(much
Hi,
I'm trying to build an LKM for the MCF5275 Edge Port Module, based on
Phil Wilshire's which was posted a while back. His was written for
2.4, but I'm using 2.6, so of course the module build process is
different. I'm getting an error during the MODPOST stage and I'm
wondering if anyone
On Wed, Mar 12, 2008 at 8:26 PM, David van Geest
[EMAIL PROTECTED] wrote:
1) When qspi_internal_write() is called, things proceed as they should
(for a while), but I can't get a blessed thing to show on an oscope.
This one is solved... wasn't setting the PAR register to enable the
QSPI pins
On Wed, Mar 12, 2008 at 8:26 PM, David van Geest
[EMAIL PROTECTED] wrote:
2) A couple lines later, sleep_on(wqueue) puts the process to sleep
(to wait for the qspi transfer to finish), and it never gets woken
again.
Also solved. Added lines in init to enable interrupt, set level
On Thu, Mar 13, 2008 at 8:48 PM, Greg Ungerer [EMAIL PROTECTED] wrote:
Hi David,
David van Geest wrote:
Also, request_irq uses SA_INTERRUPT... which doesn't seem to be
defined in 2.6.x. I added my own define for what it was in 2.4.x, but
should I be using something else?
Use
Specifically, I want to know what uClinux interrupt line is mapped to
MCF5275 interrupt 18 (the QSPI interrupt).
For example, QSPI interrupt, which is source 18 on INTC0 would
be vector 64+18, so vector 82.
Thanks for your help, Greg. That magic 64 number is what I need.
-David
Hi all,
Some background: I'm trying to use the mcf_qspi driver on an MCF5275
with 2.6.x. Originally, I had some problems compiling it, but after a
bit of hacking, it's compiling and initializing at boot. I've created
a /dev/qspi node in the ROMFS, and open() and ioctl() seem to be
working.
Hi,
Can anyone tell me where to find the MCF5275 Interrupt Vector Table?
Specifically, I want to know what uClinux interrupt line is mapped to
MCF5275 interrupt 18 (the QSPI interrupt).
Thanks,
-David
___
uClinux-dev mailing list
On Sat, Mar 1, 2008 at 3:02 PM, Jorge Pereira [EMAIL PROTECTED] wrote:
very uggly buddy, try below.
1) change your code
- #include
/home/rr/uCLinux/uClinux-dist/user/lm_sensors/kernel/include/i2c-dev.h
+ #include i2c-dev.h
2) in your compile, add parammenter.
Hi,
I'm wondering what files I need to include in a user application to
access a char device using the open(), ioctl(), write(), etc.
Searching the web, it seems like I need some combination of these files:
#includeunistd.h
#includesys/types.h
#includesys/stat.h
#includefcntl.h
#include
On Fri, Feb 29, 2008 at 11:15 AM, Harry Gunnarsson [EMAIL PROTECTED] wrote:
It looks about right, I am looking at one of my own source files that calls
the functions you refer to and I include
Thanks Harry, turns out the order does matter a lot. This is what I
have, for anyone else who's
showed up in
i2c-mcf.c. Is it expected that you define these pointers yourself, or
am I doing something wrong here?
Thanks,
-David van Geest
[ Rhythm Reloaded ]
www.rhythmreloaded.com
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http
On Feb 18, 2008 7:42 PM, David van Geest [EMAIL PROTECTED] wrote:
drivers/i2c/busses/i2c-mcf.c:94: error: MCF_I2C_I2CR undeclared (first
use in this function)
Sorry, should have Googled - just found Steve Bennet's patch to define
the names.
-David
Thanks for your replies, I just want to make sure I'm understanding
everything correctly here:
You could probably backport the 2.6.x driver to 2.4.x fairly easily.
Depends on how many of the new toys it uses :)
There is not a driver in 2.4.x that will work with Coldfire I2C? I'm
a little
PS: I had posted this problem also on [EMAIL PROTECTED], but got no
answer. I admit, the question is not really coldfire-specific. But does
this explain the silence?
Bob - You did get a response on the Coldfire list, see
http://www.nabble.com/Mess-with-library-to15068815.html. Check your
Hi all,
I'm a bit new at embedded programming, so bear with me a bit. I'm running
uClilnux on the Freescale M5275EVB, and I have a couple of questions:
1. What are the options for including custom user software on the board?
Is it necessary to re-compile the kernel with your app included every
Thanks Gavin, that clears up a lot of things for me :-)
On Nov 14, 2007 4:48 PM, Gavin Lambert [EMAIL PROTECTED] wrote:
Quoth David van Geest:
1. What are the options for including custom user software on the board?
Is it necessary to re-compile the kernel with your app included every
20 matches
Mail list logo