[ptxdist] unrecognized option 'plugin'
I'm trying to use the ppp driver. In my console output I get the following error: Starting pppd... /usr/sbin/pppd: In file /etc/ppp/options: unrecognized option 'plugin' failed Inside the /etc/ppp/options file its using the following plugin. # # Use the PPPoE plugin # plugin rp-pppoe.so The rp-pppoe.so file is where its supposed to be /root/usr/lib/pppd/2.4.4 but it seems like the ppp driver does not recognize the 'plugin' option (like the error states) What could this be and how can I rectify it? -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] unrecognized option 'plugin'
On Tue, May 15, 2012 at 9:59 AM, Michael Olbrich wrote: > On Tue, May 15, 2012 at 08:16:16AM -0700, MC Potgieter wrote: >> I'm trying to use the ppp driver. In my console output I get the >> following error: >> >> Starting pppd... >> /usr/sbin/pppd: In file /etc/ppp/options: unrecognized option 'plugin' >> failed >> >> Inside the /etc/ppp/options file its using the following plugin. >> >> # >> # Use the PPPoE plugin >> # >> plugin rp-pppoe.so >> >> The rp-pppoe.so file is where its supposed to be /root/usr/lib/pppd/2.4.4 >> but it seems like the ppp driver does not recognize the 'plugin' >> option (like the error states) >> >> What could this be and how can I rectify it? > > What's the output of > > $ grep PLUGIN= platform-*/build-target/ppp-2.4.4/pppd/Makefile > > Michael > > -- > Pengutronix e.K. | | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | > > -- > ptxdist mailing list > ptxdist@pengutronix.de grep PLUGIN= platform-*/build-target/ppp-2.4.4/pppd/Makefile PLUGIN=y But I've commented the line conatining "plugin rp-pppoe.so" because I'm not using PPPoE, I'm using a GSM modem over serial. Hope not this is a mistake. Now I get an error: Starting pppd... /usr/sbin/pppd: In file /etc/ppp/options: unrecognized option 'active-filter' failed MC -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Ptxdist upgrade
I've been on ptxdist 2011.0.0 for quite a while now and would like to upgrade to 2012.05.0 but I'm running into small problems and would appreciate your assistance. When I run ./configure it stops at: checking for patch... no configure: error: Please specify the location of patch with the option '--with-patch' -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Ptxdist upgrade
On Wed, May 16, 2012 at 5:59 AM, MC Potgieter wrote: > I've been on ptxdist 2011.0.0 for quite a while now and would like to > upgrade to 2012.05.0 but I'm running into small problems and would > appreciate your assistance. > > When I run ./configure it stops at: > > checking for patch... no > configure: error: Please specify the location of patch with the option > '--with-patch' I am following the Application note "Installing PTXdist-2011.11.0" -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Building a older version toolchain using a a newer version ptxdist
I'm trying to build the latest available combination of tools (ptxdist, BSP and toolchain) My versions are (this is the latest available tools): ptxdist: 2012.05.0 oselas toolchain: 2011.11.0 oselas BSP: 2012.02.0 After installing ptxdist I configure the toolchain: ptxdist select ptxconfigs/arm-v4t-linux-gnueabi_gcc-4.6.2_glibc-2.14.1_binutils-2.21.1a_kernel-2.6.39-sanitized.ptxconfig and then try and build it, but I get: error: The ptxconfig file version and ptxdist version do not match: configfile version: 2011.11.0 ptxdist version:2012.05.0 Which ptxconfig should I select to get matching versions (where is it located)? Or should I force the build? -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Building a older version toolchain using a a newer version ptxdist
On Wed, May 16, 2012 at 9:56 AM, MC Potgieter wrote: > I'm trying to build the latest available combination of tools > (ptxdist, BSP and toolchain) > > My versions are (this is the latest available tools): > > ptxdist: 2012.05.0 > oselas toolchain: 2011.11.0 > oselas BSP: 2012.02.0 > > After installing ptxdist I configure the toolchain: > > ptxdist select > ptxconfigs/arm-v4t-linux-gnueabi_gcc-4.6.2_glibc-2.14.1_binutils-2.21.1a_kernel-2.6.39-sanitized.ptxconfig > > and then try and build it, but I get: > > error: The ptxconfig file version and ptxdist version do not match: > > configfile version: 2011.11.0 > ptxdist version: 2012.05.0 > > Which ptxconfig should I select to get matching versions (where is it > located)? > Or should I force the build? Or should I make a symbolic link inside the toolchain folder (OSELAS.Toolchain-2011.11.1) to the ptx folder (ln -s /usr/local/bin/ptxdist-2012.05.0)? -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Building a older version toolchain using a a newer version ptxdist
On Wed, May 16, 2012 at 10:39 AM, Juergen Beisert wrote: > MC Potgieter wrote: >> I'm trying to build the latest available combination of tools >> (ptxdist, BSP and toolchain) >> >> My versions are (this is the latest available tools): >> >> ptxdist: 2012.05.0 >> oselas toolchain: 2011.11.0 >> oselas BSP: 2012.02.0 >> >> After installing ptxdist I configure the toolchain: >> >> ptxdist select >> ptxconfigs/arm-v4t-linux-gnueabi_gcc-4.6.2_glibc-2.14.1_binutils-2.21.1a_kernel-2.6.39-sanitized.ptxconfig >> >> and then try and build it, but I get: >> >> error: The ptxconfig file version and ptxdist version do not match: >> >> configfile version: 2011.11.0 >> ptxdist version: 2012.05.0 >> >> Which ptxconfig should I select to get matching versions (where is it >> located)? Or should I force the build? > > Building every OSELAS.Toolchain-2011.11.0/1 is tested with PTXdist-2011.11.0. > If > you want to be safe, install PTXdist-2011.11.0 and build the toolchain with > this version. > If you are brave, you can force the build also with the PTXdist-2012.05.0. > Most of the time it will work, but this version combination is not tested > here. > So, in case of trouble we will blame you ;) > > Regards, > Juergen > > -- > Pengutronix e.K. | Juergen Beisert | > Linux Solutions for Science and Industry | http://www.pengutronix.de/ | > > -- > ptxdist mailing list > ptxdist@pengutronix.de Hi Juergen, Then what about the BSP? Will I have to use the 2011.11.0 BSP too? I want to take advantage of the latest packages available in the latest BSP (2012.02.0). If I'm going to compile BSP 2012.02.0 when using ptx 2011 and toolchain 2011 it is going to give me the same error. What should I do? What combination of tools should I use to compile the latest BSP? MC -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Building a older version toolchain using a a newer version ptxdist
On Wed, May 16, 2012 at 10:50 AM, MC Potgieter wrote: > On Wed, May 16, 2012 at 10:39 AM, Juergen Beisert wrote: >> MC Potgieter wrote: >>> I'm trying to build the latest available combination of tools >>> (ptxdist, BSP and toolchain) >>> >>> My versions are (this is the latest available tools): >>> >>> ptxdist: 2012.05.0 >>> oselas toolchain: 2011.11.0 >>> oselas BSP: 2012.02.0 >>> >>> After installing ptxdist I configure the toolchain: >>> >>> ptxdist select >>> ptxconfigs/arm-v4t-linux-gnueabi_gcc-4.6.2_glibc-2.14.1_binutils-2.21.1a_kernel-2.6.39-sanitized.ptxconfig >>> >>> and then try and build it, but I get: >>> >>> error: The ptxconfig file version and ptxdist version do not match: >>> >>> configfile version: 2011.11.0 >>> ptxdist version: 2012.05.0 >>> >>> Which ptxconfig should I select to get matching versions (where is it >>> located)? Or should I force the build? >> >> Building every OSELAS.Toolchain-2011.11.0/1 is tested with >> PTXdist-2011.11.0. If >> you want to be safe, install PTXdist-2011.11.0 and build the toolchain with >> this version. >> If you are brave, you can force the build also with the PTXdist-2012.05.0. >> Most of the time it will work, but this version combination is not tested >> here. >> So, in case of trouble we will blame you ;) >> >> Regards, >> Juergen >> >> -- >> Pengutronix e.K. | Juergen Beisert | >> Linux Solutions for Science and Industry | http://www.pengutronix.de/ | >> >> -- >> ptxdist mailing list >> ptxdist@pengutronix.de > > Hi Juergen, > > Then what about the BSP? Will I have to use the 2011.11.0 BSP too? > I want to take advantage of the latest packages available in the > latest BSP (2012.02.0). > If I'm going to compile BSP 2012.02.0 when using ptx 2011 and > toolchain 2011 it is going to give me the same error. > > What should I do? What combination of tools should I use to compile > the latest BSP? > > MC Or is the BSP compiled independent of the ptx and toolchain versions? -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] CP2102 Driver Update
I'm using prxdist 2011.05 with Mini2440 BSP 2011.05 I would like to update my CP2102 USB Serial Driver. I've downloaded the latest driver from : http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx Looking at the /build-target/linux-2.6.38/drivers/usb/serial It does not seem like the CP2102 has any dependancies other than the cp2102.c source file. What I've done is I made a backup of the old driver source file and copied the new one. I've dropped ther kernel comilation ptxdist drop kernel.compile and then re-compiled it but it does not seem like the new cp2102 drivers source was compiled. 1.) Is this the correct way to update the driver source? 2.) How can I ensure that the new source is compiled when compiling the kernel? Thank you MC -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] How to access peripherals and IO from C code
Hi Juergen,
In the FriendlyARM linux examples they show that the LEDs (IO) can be
accessed in the following manner:
#include
#include
#include
#include
int main(int argc, char **argv)
{
int led_state = 1;
int led_no = 0;
int fd;
fd = open("/dev/leds0", 0);
if (fd < 0) {
fd = open("/dev/leds", 0);
}
if (fd < 0) {
perror("open device leds");
exit(1);
}
ioctl(fd, led_state, led_no);
close(fd);
return 0;
}
In the oselas documentation they show one can access the leds through
/sys/class/leds. How would one access the peripherals or IOs in PTXdist
using C?
Is there any example programs?
--
ptxdist mailing list
ptxdist@pengutronix.de
[ptxdist] New Display Kernel Patch
I'm using the following display with my mini2440: SP035GT - http://www.rongendisplay.com/upload/SP035GT-07OK.pdf I bought the display from: http://www.developmentboard.net/displays/19-5-tft-display.html I'm using this display because it has a landscape orientation. Hiteg does provide a kernel patch for this display (see attached patch). With standard kernel compilation I would apply the patch using diff on /arch/arm/mach-s3c2440/mach-mini2440.c Before I execute "ptxdist go" there is no /platform-mini2440/build-target/linux-2.6.37 directory so I cant apply the patch because the files does not exist. Only after ptxdist go has been completed the directory /platform-mini2440/build-target/linux-2.6.37 exist and I can apply the patch to /arch/arm/mach-s3c2440/mach-mini2440.c BUT All the files has already been built and nothing can be built anymore When "ptxdist go" has been completed, how can I apply the patch to the kernel and re-compile the kernel only? linux-2.6.37-megadisplay.patch Description: Binary data -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Running Qt example generates ": driver not found Aborted"
In the "ptxdist menuconfig" I've selected to include the following: Graphics & Multimedia -->qt -->Qt Embedded Examples -->dialogs -->standard dialog in ptx I browse to the examples directory: cd /usr/bin/qt4-examples/dialogs/standarddialogs and then execute the app using: ./standarddialogs -qws but I get the following message: : driver not found Aborted What is causing this problem? -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Running Qt example generates ": driver not found Aborted"
target path On Tue, Jun 28, 2011 at 4:28 PM, MC Potgieter wrote: > target path > > > On Tue, Jun 28, 2011 at 4:11 PM, Juergen Beisert wrote: > >> MC Potgieter wrote: >> > In the "ptxdist menuconfig" I've selected to include the following: >> > >> > Graphics & Multimedia >> > -->qt >> > -->Qt Embedded Examples >> > -->dialogs >> > -->standard dialog >> > >> > in ptx I browse to the examples directory: >> > >> > cd /usr/bin/qt4-examples/dialogs/standarddialogs >> >> Host or target path? >> >> > and then execute the app using: >> > >> > ./standarddialogs -qws >> > >> > but I get the following message: >> > : driver not found >> >> Maybe "strace" could be your friend here. >> >> jbe >> >> -- >> Pengutronix e.K. | Juergen Beisert >> | >> Linux Solutions for Science and Industry | Phone: >> +49-5121-206917-5128 | >> Vertretung Sued/Muenchen, Germany | Fax: >> +49-5121-206917- | >> Amtsgericht Hildesheim, HRA 2686 | >> http://www.pengutronix.de/ | >> > > -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Running Qt example generates ": driver not found Aborted"
I'm still having this problem and don't know how to resolve it Can you help me please? On Tue, Jun 28, 2011 at 10:13 PM, Juergen Beisert wrote: > Hi MC Potgieter, > > MC Potgieter wrote: > > its a an example program. I dont know what it is doing. > > attached is my config file > > > > thank you > > As Micheal already stated: You did not enable any driver Qt needs to draw > something. > > Graphics & Multimedia ---> > qt ---> > graphics driver ---> >LinuxFb (none ) <<< select "builtin" here instead of "none" > keyboard drivers ---> >[*] Linux Input <<< enable this if you want to use the key buttons on > the > Mini2440 > mouse drivers ---> >[*] Tslib <<< you already did > > Juergen > > -- > Pengutronix e.K. | Juergen Beisert > | > Linux Solutions for Science and Industry | Phone: +49-5121-206917-5128 > | > Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917- > | > Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ | > -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] console has access to folders which is not visible when viewed on the host
I'm loading my rootfs over nfs. I've included the qt examples to the ptx dist and they should reside in /usr/bin/qt4-examples. My nfs server exports /platform-2440/root On the server when I browse to /platform-mini2440/root/usr/bin I cant see any qt4-examples directory BUT on the target, when I cd to /usr/bin , the qt4-exmples directory is visible. No my question is, if the target is loading from the exact same root directory, why is qt4-examples visible on the target but not on the host? -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Start your own application at system start
Hi Juergen, Thank you very much. This ptx dist seems to be very powerful and flexible. Good work! I almost have all the tools I require. One of the big outstanding items is documentation or examples for peripheral initialization and control in C. You have given me an example for the IO control but I still need info on the following: - Serial (UART) - Ethernet - Timers - Delays (builtin if any) - Threads - Interrupts for all peripheral events Thank you very much MC On Thu, Jun 30, 2011 at 12:18 PM, Juergen Beisert wrote: > Hi MC Potgieter, > > please find attached two files to get your own application ran at system > start. > > Create a "rules/" directory in your Mini2440 PTXdist project, copy these > files > into it and run "ptxdist menuconfig" after that. > > These files will create a new menu entry in > > Root Filesystem ---> > [*] init ---> >< > startup script (NEW) > > Tick this box to enable it. > > Then create a simple script which starts your application you need. Name > this > script "startup" and store it in your Mini2440 PTXdist project at the > location "projectroot/home/" (you must create these directories if they do > not already exists). > > After that, run a "ptxdist go". This will install some new files on your > target root filesystem: > > - /etc/init.d/startup > - /etc/rc.d/S99startup (which points to ../init.d/startup) > - /home/startup > > If you now start your target, the init process will call your /home/startup > as > the last action after bring up the other parts of your system > > BTW: By adding new *.in and *.make files in the project's local rules/ > directory you can extend PTXdist according to your own needs. > > Regards, > Juergen > > -- > Pengutronix e.K. | Juergen Beisert > | > Linux Solutions for Science and Industry | http://www.pengutronix.de/ | > -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Start your own application at system start
Yes, that was one of the main reasons for selecting to use the linux kernel
and OS, to eliminate driver development for peripherals such as ethernet and
file system support which can be time consuming at an embedded level.
But still I need to manipulate these peripherals even if it only their
parameters/settings.
I've been working through the kernel documentation but cant get to the
bottom of things.
Lets take for example the UART baudrate, how do I set that? It will be a
file write procedure for the UART settings, but which file?
I've been looking at the examples from friendlyarm. Is the ptx peripheral
control the same or is it different?
lets take a simple uart example from the friendlyarm examples:
struct termios TtyAttr;
struct termios BackupTtyAttr;
CommFd = open("/dev/ttyS0", O_RDWR, 0);
memset(&TtyAttr, 0, sizeof(struct termios));
TtyAttr.c_iflag = IGNPAR;
TtyAttr.c_cflag = DeviceSpeed | HUPCL | ByteBits | CREAD | CLOCAL;
TtyAttr.c_cc[VMIN] = 1;
TtyFd = open("/dev/tty", O_RDWR | O_NDELAY, 0);
TtyAttr.c_cflag = TtySpeed | HUPCL | ByteBits | CREAD | CLOCAL;
tcsetattr(TtyFd, TCSANOW, &TtyAttr)
>From these example there is struct, where can I find a prototype of the
struct to know what parameters it can take?
In the struct is a c_clag parameter. Where can I find a list of supported
flags?
Then there is tcsetattr function, where can I find a prototype of the
function with a description of parameters that is passed to it?
Clearly the kernel provides an abstraction layer or library through which I
can access the peripherals.
I honestly have been working through the kernel documentation but could not
find relevant information.
I'm not asking ptx because I need ptx to give me the answers, I'm asking ptx
because I'm not sure whether your peripheral abstraction layer is different
from other kernel branches.
Will you please be so kind as to direct me or guide me to the relevant
literature.
Thank you
On Thu, Jun 30, 2011 at 2:36 PM, Josef Holzmayr <
holzm...@rsi-elektrotechnik.de> wrote:
> > I almost have all the tools I require. One of the big outstanding items
> is
> > documentation or examples for peripheral initialization and control in C.
> > You have given me an example for the IO control but I still need info on
> the
> > following:
> >
> > - Serial (UART)
> > - Ethernet
> > - Timers
> > - Delays (builtin if any)
> > - Threads
> > - Interrupts for all peripheral events
>
> I guess the better approach is to have a thorough look at the linux kernel
> drivers and their infrastructure. PTXdist is meant for building an embedded
> _linux_ system, where linux means you have an os kernel that handles this
> stuff for you and provides an abstract, stable interface to it.
>
> For example taking the UARTs:
> they get provided as /dev/tty* nodes. You just use them like any other
> file, no need to do some initialization/control stuff like in the embedded
> market (where you obviously come from).
>
> The already existing device drivers will probably make up ~99.5% of all
> your hardware handling code, and for the rest there's things like UIO, for
> example.
>
> But it's really essential to get your head around the OS kernel thing and
> stop thinking embedded.
>
> Greetz Sepp
>
> Dipl-Ing. (FH) J. Holzmayr
> Entwicklung Embedded Devices / Software
>
> Telefon: (08444) 9204-48
> Telefax: (08444) 9204-50
>
> R-S-I Elektrotechnik GmbH & Co. KG
> Woelkestrasse 11
> 85301 Schweitenkirchen
> Germany
>
>
> Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
> Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
> USt-IdNr.: DE 128592548
>
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
ptxdist mailing list
ptxdist@pengutronix.de
Re: [ptxdist] Start your own application at system start
Thank you 2011/6/30 Josef Holzmayr > Addendum: > > man termios. > > > Dipl-Ing. (FH) J. Holzmayr > Entwicklung Embedded Devices / Software > > Telefon: (08444) 9204-48 > Telefax: (08444) 9204-50 > > R-S-I Elektrotechnik GmbH & Co. KG > Woelkestrasse 11 > 85301 Schweitenkirchen > Germany > > > Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363 > Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg > USt-IdNr.: DE 128592548 > > > > -- > ptxdist mailing list > ptxdist@pengutronix.de > -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Qt and mini2440 BSP
I also had some strange behavior after changing settings for Qt. I also had to start from scratch to restore order. Does this mean Arora is now working? On Tue, Jul 5, 2011 at 9:12 AM, Dave wrote: > Qt problems on PTXdist 06 > > > > After a compilation of my "own" Qt project (/demos/browser), following > > instructions posted and adding another mouse driver in Qt things started > > to go wrong. My efforts to restore proper operation consisted of doing > > the following: > > > > $ ptxdist clean browser > > $ ptxdist clean qt4 > > $ ptxdist clean root > > then > > $ ptxdist go > > > > deleting the four "unwanted" .qmake.cache files in > > > > build-host/qt-everywhere-opensource-src-4.6.3-build > > build-host/qt-everywhere-opensource-src-4.6.3-build/config.test > > build-target/qt-everywhere-opensource-src-4.6.3-build > > build-target/qt-everywhere-opensource-src-4.6.3-build/config.test > > > > then > > $ ptxdist go > > > > deleting folders > > > > build-host/qt-everywhere-opensource-src-4.6.3-build > > build-host/qt-everywhere-opensource-src-4.6.3-src > > build-target/qt-everywhere-opensource-src-4.6.3-build > > build-target/qt-everywhere-opensource-src-4.6.3-src > > > > then > > $ ptxdist go > > > > A common error message was: > > > > /home/davef/Pengutronix-6/OSELAS.BSP-Pengutronix-Mini2440-2011.06.0/ > > platform-mini2440/sysroot-target/usr/lib/ > > libQtCore.a(qlibrary_unix.o): In function `qdlerror()': > > qlibrary_unix.cpp:(.text+0x88): undefined reference to `dlerror' > > > > . > > > > /opt/OSELAS.Toolchain-2011.03.0/arm-v4t-linux-gnueabi/ > > gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/lib/gcc/ > > arm-v4t-linux-gnueabi/4.5.2/../../../../arm-v4t-linux-gnueabi/bin/ > > ld: warning: creating a DT_TEXTREL in object. > > collect2: ld returned 1 exit status > > make[2]: Leaving directory `/home/davef/Pengutronix-6/ > > OSELAS.BSP-Pengutronix-Mini2440-2011.06.0/platform-mini2440/build-target/ > > qt-everywhere-opensource-src-4.6.3-build/src/network' > > make[1]: Leaving directory `/home/davef/Pengutronix-6/ > > OSELAS.BSP-Pengutronix-Mini2440-2011.06.0/platform-mini2440/build-target/ > > qt-everywhere-opensource-src-4.6.3-build' > > make[2]: *** [../../lib/libQtNetwork.so.4.6.3] Error 1 > > make[1]: *** [sub-network] Error 2 > > make: *** [/home/davef/Pengutronix-6/ > > OSELAS.BSP-Pengutronix-Mini2440-2011.06.0/platform-mini2440/ > > state/qt4.compile] Error 2 > > davef@davef-desktop > :~/Pengutronix-6/OSELAS.BSP-Pengutronix-Mini2440-2011.06.0$ > > > > I suspect this is possibly the first instance of a Qt library being > > cross-compiled. > > > > Next, I deleted OSELAS.BSP-Pengutronix-Mini2440-2011.06.0 and started > > over again. This time I checked basic kernel operation and then added > > Qt and the Qt options to support Arora. Having previously cross-compiled > > /demos/browser using the PTXdist toolchain I just dropped it's binary into > > /usr/bin and the program runs properly. > > > > So, the question is how should one reclaim a BSP after it has obviously > been > > corrupted because of failed attempts at cross-compiling Qt? > > > > > > > > > > > > > > > -- > ptxdist mailing list > ptxdist@pengutronix.de > -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] Memory Status
Hi, I'm using PTXdist on my mini2440. How can I determine how much RAM is available for my use (user application). Thank you -- ptxdist mailing list ptxdist@pengutronix.de
