Re: [uClinux-dev] Toolchain for ARM uClinux-2.6 kernel/userland

Hi KJ, Lin KJ wrote: > Thanks for your detailed explanation. > > I can use the arm-linux toolchain to build everything in the uClinux-dist. > However, how should i do if i want to build other open source packages or > applications which are not in the uClinux-dist? > For example, microwindows or

[uClinux-dev] Re: Re : arm7tdmi - NXP LPC2468 - gcc/g++/libstdc++, it's possible?

How did you build the uClibc and stdc+++ you link against to? Jorge Pereira wrote: > i used this! > > :( > > On Fri, Mar 7, 2008 at 10:36 AM, Aníbal Pinto <[EMAIL PROTECTED] > > wrote: > > hi, > > try with this toolchain : http://www.codesourcery.com/gnu_toolc

Re: [uClinux-dev] Toolchain for ARM uClinux-2.6 kernel/userland

Hi Greg, Thanks again. Putting the stand alone apps in the uClinux-dist to compile is easy but seems not very convenient. How about the "arm-elf" toolchain? Is it the same? Can i use the arm-elf toolchain to compile my own application directly? KJ 寄件者： Greg Ungerer <[EMAIL PROTECTED]> 收件者： u

Re: [uClinux-dev] Itimer resolution

On Tuesday 11 March 2008 19:19:21 Sean McGranaghan wrote: > Hello all, > > I am evaluating the M5208EVB for a customer. My test application uses an > interval timer for some coarse grained timing. I initialize the timer as > follows: > > memset(&itimer, 0, sizeof(itimer)); > itimer.it_inter

[uClinux-dev] WhoamI

Hi all when uClinux is up and running, I can enter commands via the serial I/F (COBRA5282-board). I then mount the workspace-folder of my linux-host to /usr of the target. When I then want to run my program it fails (see terminal-output below), because I do not have the correct permissions. But cha

Re: [uClinux-dev] WhoamI

On Wednesday 12 March 2008 11:00:40 Robert Brusa wrote: > Hi all > when uClinux is up and running, I can enter commands via the serial I/F > (COBRA5282-board). I then mount the workspace-folder of my linux-host > to /usr of the target. When I then want to run my program it fails (see > terminal-out

Re: [uClinux-dev] WhoamI

Am Mittwoch, den 12.03.2008, 11:09 +0200 schrieb Bongani Hlope: > On Wednesday 12 March 2008 11:00:40 Robert Brusa wrote: > > Hi all > > when uClinux is up and running, I can enter commands via the serial I/F > > (COBRA5282-board). I then mount the workspace-folder of my linux-host > > to /usr of t

[uClinux-dev] generating the Kernel-Doc

Hi all The file uClinux-dist/linux-2.6.x/Documentation/kernel-doc-nano-HOWTO.txt tells me, that in order to generate the kernel doc, I should run the command "make pdfdocs". Well I do it and here is what I get: > [EMAIL PROTECTED]:~/uClinux-dist/linux-2.6.x/Documentation/DocBook$ make > pdfdocs

Re: [uClinux-dev] Toolchain for ARM uClinux-2.6 kernel/userland

Jivin Lin KJ lays it down ... > Hi Greg, > > Thanks again. > > Putting the stand alone apps in the uClinux-dist to compile is easy but seems > not very convenient. > > How about the "arm-elf" toolchain? Is it the same? > Can i use the arm-elf toolchain to compile my own application directly? Y

Re: [uClinux-dev] Toolchain for ARM uClinux-2.6 kernel/userland

Greg Ungerer wrote: > > By the way, should i use the "linux-2.6.24-uc0.patch" from uclinux as my > > kernel porting start point? > > Or use the "linux-2.6.14-hsc0.patch" from the uClinux/ARM2.6 > > project(http://opensrc.sec.samsung.com/)? > > In fact, the two projects confuse me. > > Up to you

Re: [uClinux-dev] Toolchain for ARM uClinux-2.6 kernel/userland

> Putting the stand alone apps in the uClinux-dist to compile is easy > but seems not very convenient. How about the "arm-elf" toolchain? > Is it the same? Can i use the arm-elf toolchain to compile my own > application directly? As I've seen, the arm-elf toolchain is older than arm-uclinux. Th

Re: [uClinux-dev] where is the MCF5275 Interrupt Vector Table?

> > 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

Re: [uClinux-dev] Toolchain for ARM uClinux-2.6 kernel/userland

You point out the "arm-uclinux". Besides the "arm-linux" and "arm-elf", is there also a "arm-uclinux" toolchain for ARM uClinux-2.6 world? I can get the "arm-linux" from Snapgear and "arm-elf" from uclinux.org. Where can i get the "arm-uclinux" toolchain? KJ - 原始信件 寄件者： Jamie Lokier <[

[uClinux-dev] i2c slave mode on mcf5282

Scanning the uClinux code base I realized that the I2C slave functionality isn't yet implemented in the uClinux sources (and neither in the linux kernel when I search the web) or did I miss something? Did anyone crash into the same troubles and can give me an advice or some pointers? I'd lik

[uClinux-dev] interrupts and the mcf_qspi.c driver on the MCF5275

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. Whil

Re: [uClinux-dev] Toolchain for ARM uClinux-2.6 kernel/userland

Hi Jamie, Jamie Lokier wrote: Greg Ungerer wrote: By the way, should i use the "linux-2.6.24-uc0.patch" from uclinux as my kernel porting start point? Or use the "linux-2.6.14-hsc0.patch" from the uClinux/ARM2.6 project(http://opensrc.sec.samsung.com/)? In fact, the two projects confuse me.

Re: [uClinux-dev] Toolchain for ARM uClinux-2.6 kernel/userland

Hi KJ, Lin KJ wrote: > Thanks again. > > Putting the stand alone apps in the uClinux-dist to compile is easy but seems > not very convenient. I find it much quicker to drop them into the uClinux-dist. Otherwise you need to make sure you get the build options right (and many people don't get the

Re: [uClinux-dev] [PATCH] elf2flt: new --with-binutils-build-dir configure flag

On Thursday 21 February 2008, David McCullough wrote: > If it's possible to do this using installed versions then it does sound > better, and probably much easier to get right :-) does that mean you're gonna merge it ? ;) -mike signature.asc Description: This is a digitally signed message part.

Re: [uClinux-dev] [PATCH] elf2flt: new --with-binutils-build-dir configure flag

Jivin Mike Frysinger lays it down ... > On Thursday 21 February 2008, David McCullough wrote: > > If it's possible to do this using installed versions then it does sound > > better, and probably much easier to get right :-) > > does that mean you're gonna merge it ? ;) I guess it does :-), app

Re: [uClinux-dev] [Fwd: convert ld-elf2flt to C program]

On Wednesday 20 February 2008, Mike Frysinger wrote: > On Tuesday 12 September 2006, Nathan Sidwell wrote: > > static void fatal (const char *, ...); > > static void fatal_perror (const char *, ...); > > are there really no libiberty funcs that do this ? looks like the binutils peeps are lazy and

RE: [uClinux-dev] [Fwd: convert ld-elf2flt to C program]

Quoth Mike Frysinger: > On Wednesday 20 February 2008, Mike Frysinger wrote: > > On Tuesday 12 September 2006, Nathan Sidwell wrote: > > > static void fatal (const char *, ...); static void fatal_perror > > > (const char *, ...); > > > > are there really no libiberty funcs that do this ? > > looks

Re: [uClinux-dev] [PATCH] elf2flt: new --with-binutils-build-dir configure flag

On Thursday 13 March 2008, David McCullough wrote: > Jivin Mike Frysinger lays it down ... > > On Thursday 21 February 2008, David McCullough wrote: > > > If it's possible to do this using installed versions then it does sound > > > better, and probably much easier to get right :-) > > > > does th

Re: [uClinux-dev] [PATCH] elf2flt: new --with-binutils-build-dir configure flag

Jivin Mike Frysinger lays it down ... > On Thursday 13 March 2008, David McCullough wrote: > > Jivin Mike Frysinger lays it down ... > > > On Thursday 21 February 2008, David McCullough wrote: > > > > If it's possible to do this using installed versions then it does sound > > > > better, and prob

Re: [uClinux-dev] [Fwd: convert ld-elf2flt to C program]

On Thursday 13 March 2008, Gavin Lambert wrote: > Quoth Mike Frysinger: > > On Wednesday 20 February 2008, Mike Frysinger wrote: > > > On Tuesday 12 September 2006, Nathan Sidwell wrote: > > > > static void fatal (const char *, ...); static void fatal_perror > > > > (const char *, ...); > > > > > >