Re: [oselas] Latest mini2440BSP bash pidof problems

2015-03-02 Thread dave festing
Yes, it does. > From: j...@pengutronix.de > To: oselas@community.pengutronix.de > Date: Mon, 2 Mar 2015 11:19:55 +0100 > CC: dave_fest...@hotmail.com > Subject: Re: [oselas] Latest mini2440BSP bash pidof problems > > On Saturday 28 February 2015 08:11:20 Dave Festing wrote:

Re: [oselas] Latest mini2440BSP bash pidof problems

2015-03-02 Thread dave festing
The penny just dropped, if I do: pidof php5 data.php the PID is returned. Looks like the initial problem ... ie from the directory that data.php is in, that it couldn't be invoked by ./data.php but worked with php5 data.php seems to influence how pidof now works. Well, looks like I have a work

Re: [oselas] Latest mini2440BSP bash pidof problems

2015-03-02 Thread dave festing
.de > To: oselas@community.pengutronix.de > Date: Mon, 2 Mar 2015 10:30:15 +0100 > CC: dave_fest...@hotmail.com > Subject: Re: [oselas] Latest mini2440BSP bash pidof problems > > Hi Dave, > > On Saturday 28 February 2015 08:11:20 Dave Festing wrote: > > Upgraded a sy

[oselas] Latest mini2440BSP bash pidof problems

2015-02-27 Thread Dave Festing
Upgraded a system that has been working nicely with the previous BSP and 3.7 and having a few problems. My main PHP script starts with: #!/usr/bin/php5

[oselas] unable to locate package ipkg

2014-10-18 Thread Dave Festing
Upgraded from Ubuntu 10.04LTS to Xubuntu 14.04LTS on both my desktop and netbook. I can ptxdist go and ptxdist images on the Desktop but on the netbook, withptxdist images, I get the following error: davef@davef-AOD255E:~/OSELAS.BSP-Pengutronix-Mini2440-2013.10.0$ ptxdist images Creating ipkg ind

Re: [oselas] FriendlyARM mini2440: fbtest not displaying any thing on display

2014-08-04 Thread dave festing
; Framebuffer Console support[*] Map the console to the primary display device [*] Select compiled-in fonts [*] VGA 8x8 font Thanks,Girish On Sun, Aug 3, 2014 at 11:47 AM, dave festing wrote: Girish, This does sound familiar ... have you enabled virtua

Re: [oselas] FriendlyARM mini2440: fbtest not displaying any thing on display

2014-08-02 Thread dave festing
Girish, This does sound familiar ... have you enabled virtual terminal in the kernel? Device Drivers ---> Character devices ---> [*] Virtual terminal [*] Enable character translations in console [*] Support for console on virtual terminal Graphics suppor

Re: [oselas] Compiling PTXdist

2014-07-18 Thread dave festing
.git repository for further details. and some thing that said "Current release is OSELAS.BSP-Pengutronix-Mini2440-2013.10.0.tgz" any ways.. thanks for the quick response.. I'll check the link you provided. Thanks,Girish On Sat, Jul 19, 2014 at 2:17 AM, dave festing wrote:

Re: [oselas] Compiling PTXdist

2014-07-18 Thread dave festing
== There is difference in load address and entry point between the two kernels as seen above but i don't think this makes any difference.. Thanks,Girish On Fri, Jul 18, 2014 at 1:59 AM, dave festing wrote: I sometimes get errors like this on my local mirror. Is

Re: [oselas] Compiling PTXdist

2014-07-17 Thread dave festing
I sometimes get errors like this on my local mirror. Is it possible to change to another repository? Regards, Dave Date: Thu, 17 Jul 2014 23:51:18 +0530 From: dcgiris...@gmail.com To: b.buer...@pengutronix.de CC: oselas@community.pengutronix.de Subject: Re: [oselas] Compiling PTXdist Hello Bjø

[oselas] mtab

2014-06-27 Thread Dave Festing
I just happened to be looking files in /etc (mini2440 root) and noticed this entry in mtab (last line): gvfs-fuse-daemon /home/davef/.gvfs fuse.gvfs-fuse-daemon / rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 My first reaction was, because a long while ago I did have a /home/davef direc

Re: [oselas] date and hwclock not reading the same

2013-12-22 Thread Dave Festing
> OK, I have set my mini2440 hwclock to UTC. > > hwclock --show gives UTC time > hwclock -u gives local time > hwclock -l gives UTC time > > When I set the hwclock on my netbook (Ubuntu) to UTC > > hwclock --show gives UTC time > hwclock -u gives UTC time > hwclock --localtime gives

Re: [oselas] date and hwclock not reading the same

2013-12-21 Thread Dave Festing
Jürgen Beisert writes: > > > On Tuesday 17 December 2013 10:48:16 Dave Festing wrote: > > On the 9thDec - date and hwclock changed from displaying the same time to > > the hwclock being correct BUT date showing a time 13 hours ahead of my > > current local time. O

[oselas] date and hwclock not reading the same

2013-12-17 Thread Dave Festing
On the 9thDec - date and hwclock changed from displaying the same time to the hwclock being correct BUT date showing a time 13 hours ahead of my current local time. Only on my mini2440s running either the 2012.12 Pengutronix BSP or the 2013.09 version Now, 13 hours is the difference between NZD

Re: [oselas] To users of the Mini2440 BSP: bug alert -> now solved

2013-09-11 Thread Dave Festing
> Juergen, Based on your assessment of how the problem is made visible I would doubt that it is the cause of my failure. As my system also uses some USB code from Teensy and a 1-wire library from Martin Thomas running on a separate uP, which just happens to be connected to a mini2440, I feel it

Re: [oselas] To users of the Mini2440 BSP: bug alert -> now solved

2013-09-10 Thread Dave Festing
Jürgen, I should not have mentioned 1-wire. I was trying to indicate that there was some USB activity as well as few other processes running in the background. The circumstances stated for having this problem is "when using threads in their application". As far as I aware my PHP script is not u

Re: [oselas] To users of the Mini2440 BSP: bug alert -> now solved

2013-09-10 Thread Dave Festing
> All users of Linux-3.5 or later should update, to avoid unpredictable > crashes when using threads in their application. Currently, I am running thttpd, telnet and a PHP script (my application) in the background. Before I change to 3.10 and PTXdist 2013.08.0 I would like to know if doing that

Re: [oselas] Trying to download 2.6.39 ...

2013-07-26 Thread Dave Festing
> You always can run programs which are compiled against headers from older > kernels than it is currently running on your system. But not the other way. OK. That is a clear rule. > How to decide what header revisions must be used? Experience ;) and > sometimes a project lists them as a require

Re: [oselas] Trying to download 2.6.39 ...

2013-07-26 Thread Dave Festing
I should mention I see where 2.6.39 is being called in the iptables rule file and I think I know how to change to 3.7 I guess what I am asking is why is a specific kernel version called in the rule file and how do you know when it needs changing and what to change it to!

Re: [oselas] Trying to download 2.6.39 ...

2013-07-26 Thread Dave Festing
The latest version is iptables-1.4.19 Where does some code in the source tell you what kernel (headers) you should be compiling against? I have done a bit of reading about kernel headers, but haven't found a list of rules. glibc seems to be involved. Obviously, one can compile older versions

Re: [oselas] Trying to download 2.6.39 ...

2013-07-22 Thread Dave Festing
Thank you.

Re: [oselas] Trying to download 2.6.39 ...

2013-07-22 Thread Dave Festing
Jürgen Beisert writes: > > Hi Dave, > > > [...] > > I am pretty well convinced that something is enabling the 2.6.39 kernel > > headers and even you try to return to the previous setup that they are not > > removed. > > You can navigate to the kernel headers menu entry, select "help" and Kconf

Re: [oselas] Trying to download 2.6.39 ...

2013-07-22 Thread Dave Festing
David Festing writes: > > > I will just put back my previous ptxconfig file, which > > I have fortunately saved :) > > And that saved the day. I searched through old emails and see that I had a > similar problem when I tried to include RFKILL, when building WiFi support > in the kernel about

Re: [oselas] Trying to download 2.6.39 ...

2013-07-21 Thread Dave Festing
Dave Festing writes: > > but, wanting to use 3.7. > > When I ticked iptables and then ptxdist go I was told that 2.6.39.tar.xz > needed to be downloaded. > > CTRL C and disable iptables, still wants to download it. > > ptxdist clean root -> ditto > ptxdist

[oselas] Busybox chat and PPP/chat mini2440BSP

2013-07-21 Thread Dave Festing
I noticed that one can select both of these chats. Can they exist together or is the preferred option to only include one? Thanks, Dave

[oselas] Trying to download 2.6.39 ...

2013-07-21 Thread Dave Festing
but, wanting to use 3.7. When I ticked iptables and then ptxdist go I was told that 2.6.39.tar.xz needed to be downloaded. CTRL C and disable iptables, still wants to download it. ptxdist clean root -> ditto ptxdist clean kernel -> ditto I have had happen before when I was trying to get a WiFi

Re: [oselas] QT console app issue on mini2440

2013-06-29 Thread Dave Festing
amit shah writes: > > > Hi Dave      The attachment is a tgz file use winrar to untar it if you are using windows. The source is locatedSoundServer/SoundServer/ . > There is no function connectToLocalFile in it . The function could be part of QCoreApplication but I have not checked it yet.

Re: [oselas] QT console app issue on mini2440

2013-06-28 Thread Dave Festing
amit shah writes: > > Hi All,          I developing a qt based console (app) daemon  to play sound files . > I'm using QT ver 4.7.3 with a 201108 version of ptx dist. > When I launch the app with or without the -qws flag it gives me  the following error > > QWSSocket::connectToLocalFile could n

[oselas] autostart

2013-06-04 Thread Dave Festing
Appears autostart has changed since a year ago, because there is no [ ] init ---> [ ] startup script even in mini2440.BSP 2012.06.0 I tried to use rc.once.d and put the script in there but couldn't get that to work. rc.once.d seems to be a PTXdist implementation, ie there are only 5 hits on

Re: [oselas] mini2440 kernel module development

2013-04-09 Thread Dave Festing
> > > I am not proceeding with a kernel module exercise, as trying to get a ASUS > > N-10 WiFi adapter working on the mini2440 looks to be a much BIGGER job > > than I imagined. > > A real challenge? ;) > One of the challenges is that there is maybe a file called rtl8712u.bin which needs to go i

Re: [oselas] mini2440 kernel tries to revert to 2.6.39

2013-04-08 Thread Dave Festing
> > After trying to do something exciting on the mini2440 and failing I did a > ptxdist clean kernel and ptxdist clean root. > > On ptxdist go the first thing that happens is that is tries to download 2.6.39 > > The selected_platformconfig says: > > PTXCONF_KERNEL_VERSION="3.7" > > Before I cl

[oselas] mini2440 kernel tries to revert to 2.6.39

2013-04-08 Thread Dave Festing
After trying to do something exciting on the mini2440 and failing I did a ptxdist clean kernel and ptxdist clean root. On ptxdist go the first thing that happens is that is tries to download 2.6.39 The selected_platformconfig says: PTXCONF_KERNEL_VERSION="3.7" Before I clean everything out and

Re: [oselas] mini2440 kernel module development

2013-04-08 Thread Dave Festing
> > Hi, > > I have read through: > > PTXdist Application Note > Kernel Driver Development > > and it doesn't seem to apply to current versions of PTXdist. Is there a > more recent App note? > > Thanks, > Dave > > For example on page 2: project$ cd rules/ project/rules$ ptxdist newpacket

[oselas] mini2440 kernel module development

2013-04-06 Thread Dave Festing
Hi, I have read through: PTXdist Application Note Kernel Driver Development and it doesn't seem to apply to current versions of PTXdist. Is there a more recent App note? Thanks, Dave

Re: [oselas] ptxdist clean rootfs {mini2440}

2013-03-28 Thread Dave Festing
Juergen, As usual ... very well explained. Thank you! Dave

Re: [oselas] ptxdist clean rootfs {mini2440}

2013-03-27 Thread Dave Festing
Juergen Beisert writes: > > Hi Dave, > > Where should it include it? Into the "/root" or into > the images which PTXdist can create for the NAND or an SD card? > > Are these files part of the "rootfs"-package? About what files do > you talk here exactly? > > Regards, > Juergen Hi Juergen,

[oselas] ptxdist clean rootfs {mini2440}

2013-03-27 Thread Dave Festing
Hi, After not doing this for about 2 months I find that this command now does not include my files from /projectroot with a ptdist go. A ptxdist clean root does both. All the right boxes are ticked in menuconfig. First, I noticed this on a fall-back 2012.06.0 version, but it also happens on my

Re: [oselas] Backlight control

2013-02-04 Thread dave festing
on. If there is something I have missed I'd appreciate any suggestions. Cheers, Dave > From: j...@pengutronix.de > To: oselas@community.pengutronix.de > Date: Mon, 4 Feb 2013 10:31:46 +0100 > CC: dave_fest...@hotmail.com > Subject: Re: [oselas] Backlight control >

Re: [oselas] Backlight control

2013-02-02 Thread Dave Festing
> In my previous Qt work I had Framebuffer Console support enabled. Was that > incorrect? The last sentence in the above sounds like I didn't need to enable > Framebuffer Console support. Does Qt application = graphical application? Just a follow-up .. yes a Qt application works with Framebuffe

Re: [oselas] Backlight control

2013-01-31 Thread Dave Festing
> Dave Festing writes: > > Does someone know how to wake up the backlight on events other than hitting > a > key on a USB keyboard? I am running a Qt application and it would be nice > to > wake up on a mouse event. > > Or, is there a way to stop the backlight go

[oselas] Backlight control

2013-01-31 Thread Dave Festing
Does someone know how to wake up the backlight on events other than hitting a key on a USB keyboard? I am running a Qt application and it would be nice to wake up on a mouse event. Or, is there a way to stop the backlight going off from user space? I could put that in my script before running th

Re: [oselas] Barebox framebuffer driver for mini2440.

2013-01-16 Thread dave festing
http://www.cnx-software.com/2013/01/16/barebox-bootloader-status-update-elce-2012/ > Date: Wed, 16 Jan 2013 08:11:15 -0200 > From: fran...@gmail.com > To: j...@pengutronix.de > CC: oselas@community.pengutronix.de; syncopatedc...@gmail.com > Subject: Re: [oselas] Barebox framebuffer driver for min

Re: [oselas] USB powered monitor

2013-01-16 Thread dave festing
gt; CC: dave_fest...@hotmail.com > Subject: Re: [oselas] USB powered monitor > > dave festing wrote: > > Has anyone tried building support for a USB powered monitor (Dynalink USB > > framebuffer support)? > > Not yet, sorry. But if you get it run on your Linux based host

Re: [oselas] Barebox framebuffer driver for mini2440.

2013-01-15 Thread dave festing
In ptxdist kernelconfig? Graphics support -> Console display driver support -> <*> Framebuffer Console support -> [*] Map the console to the primary display device -> [*] Select compiled in fonts -> [*] VGA 8*8 font Can't answer the 2nd part. Date: Tue, 15 Jan 2013 14:20:37 -0500

[oselas] USB powered monitor

2013-01-09 Thread dave festing
Has anyone tried building support for a USB powered monitor (Dynalink USB framebuffer support)? Thanks, Dave

Re: [oselas] ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded: ignored

2013-01-09 Thread dave festing
t 11:05 AM, dave festing wrote: Have you been able to build other packages and now you can't build this one? Dave From: razi...@gmail.com Date: Wed, 9 Jan 2013 10:59:51 +0200 To: oselas@community.pengutronix.de Subject: [oselas] ERROR: ld.so: object 'libfakeroot.so' from LD_PRE

Re: [oselas] ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded: ignored

2013-01-09 Thread dave festing
Have you been able to build other packages and now you can't build this one? Dave From: razi...@gmail.com Date: Wed, 9 Jan 2013 10:59:51 +0200 To: oselas@community.pengutronix.de Subject: [oselas] ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded: ignored Hello i am tr

Re: [oselas] Nano enable nanorc

2013-01-02 Thread Dave Festing
> Juergen, Could you confirm that I used the correct procedure here? It worked but maybe ptxdist extract nano, modify config.h and ptxdist go is more appropriate. Dave

Re: [oselas] Nano enable nanorc

2013-01-02 Thread Dave Festing
> A wordaround for the problem of not handling \< and \> in the more acceptable manner has been suggested by Chris Allegretta, the Nano maintainer as follows: * You may be able to work around this by replacing the following line in config.h after running configure: /* #undef GNU_WORDBOUNDS */

Re: [oselas] [ANNOUNCE] Mini2440: Forth Quarter 2012 Release of the?Free Board Support Package is now available

2012-12-23 Thread Dave Festing
> In most cases that's because the BSP was moved. fakeroot remembers an > absolute path to die directory containing libfakeroot.so. If that changes, > fakeroot fails to find it. If that's not the case, is there a > libfakeroot.so in the PATHS specified in sysroot-host/bin/fakeroot lind 38? Oops!!!

Re: [oselas] [ANNOUNCE] Mini2440: Forth Quarter 2012 Release of the?Free Board Support Package is now available

2012-12-23 Thread Dave Festing
> After I added my own rootfs files they had to be selected in menuconfig, so yes the ptxconfig was saved after any changes. Looking at line 38 in sysroot-host/bin/fakeroot I am directed to sysroot-host/lib/fakeroot. In that directory there are 4 files: libfakeroot.a libfakeroot.la libfakeroot.

Re: [oselas] [ANNOUNCE] Mini2440: Forth Quarter 2012 Release of the Free Board Support Package is now available

2012-12-23 Thread Dave Festing
I built a basic configuration successfully, but when I added my own rootfs as per page 63 I got this error: davef@davef-laptop:~/Pengutronix2012$ ptxdist go target: libffi.targetinstall install_init: preparing for image creation of 'lib

Re: [oselas] [ANNOUNCE] Mini2440: Forth Quarter 2012 Release of the Free Board Support Package is now available

2012-12-21 Thread Dave Festing
> Hi everybody (but especially Dave Festing) > Dave, may I remember you to your email from 19.09.2012? > Quotation: "Mehmet, I will write a HowTo document that should help > reduce the risk of a heart attack! Around mid-October." > > :) > > see page 63 in the

Re: [oselas] Nano enable nanorc

2012-12-10 Thread dave festing
C: dave_fest...@hotmail.com > Subject: Re: [oselas] Nano enable nanorc > > Hi Dave, > > Dave Festing wrote: > > Just in case anyone has problems with nanorc scripts that contain \< and \> > > sequences in them. > > > > Try changing them to \b > >

[oselas] Adding static compile parameters - nano

2012-12-10 Thread Dave Festing
nano -V tells me how nano has been built by default. Looking at joe.make for hints I modified nano.make, specifically this line to include the two new options I want: # # autoconf # NANO_AUTOCONF := $(CROSS_AUTOCONF_USR) --enable-browser --enable-mouse # As I don't see any other differences be

Re: [oselas] Nano enable nanorc

2012-12-09 Thread Dave Festing
> Just in case anyone has problems with nanorc scripts that contain \< and \> sequences in them. Try changing them to \b The suggestion from the hint I found is that \< and \> not being parsed correctly could be a "libc issue".

Re: [oselas] Barebox ethernet SD card

2012-12-04 Thread Dave Festing
Juergen Beisert writes: > > Hi Dave, > > Dave Festing wrote: > > Just trying to understand the meaning of this line in /env/config > > > > # use 'ip=none' if you want to skip kernel ip configuration > > > > I have found that if I place my ne

Re: [oselas] Nano enable nanorc

2012-11-29 Thread Dave Festing
To obtain syntax hi-lighting in Nano. Using the up/down arrow keys doesn't work properly in some terminals. up/down arrow keys colour ansi doesn't work yes linux works yes screen doesn't work yes vt100

Re: [oselas] Nano enable nanorc

2012-11-29 Thread Dave Festing
Well, after an hour or so reading about different terminals and looking through /usr/share/terminfo I tried: setenv TERM=xterm, which didn't work. Then: TERM=xterm and checked with printenv and it had changed. Ran a PHP script and now there is colour!! I still am struggling to get many of t

Re: [oselas] Nano enable nanorc

2012-11-28 Thread Dave Festing
By default when building the 2.2.6 version of Nano you automatically get: --enable-nanorc and --enable-color plus two other options. I can place various versions of php.nanorc found on the www into /usr/share/nano and get hilighted text, but NOT in color. Nano syntax hilighting on the desktop w

Re: [oselas] Nano enable nanorc

2012-11-27 Thread Dave Festing
> Thank you that worked. Now, I don't have to type nano -w every time I open a file :) Next, I'll look at the syntax highlighting options.

[oselas] Nano enable nanorc

2012-11-22 Thread Dave Festing
Thought I would try enabling nanorc in nano 1.3.12 in the mini2440-2012.06.0 BSP Modified nano.in to include the option. nano.make was modified by changing the line: NANO_AUTOCONF := $(CROSS_AUTOCONF_USR) to: NANO_AUTOCONF := $(CROSS_AUTOCONF_USR) \ --enable-nanorc but get th

[oselas] Barebox ethernet SD card

2012-11-22 Thread Dave Festing
Just trying to understand the meaning of this line in /env/config # use 'ip=none' if you want to skip kernel ip configuration I have found that if I place my network parameters in /etc/network/interfaces then I need to say 'ip=none' for booting with an SD card. If I comment out my network parame

Re: [oselas] install_alternative

2012-11-05 Thread Dave Festing
> Thank you for the tip $PTXDIST_WORKSPACE. Cheers, Dave

Re: [oselas] pygame

2012-11-03 Thread dave festing
Until you get the rule file sorted try cross-compile it using the PTXdist toolchain and add it manually. I use to do that way for msmtp. thttpd and php5 before Juergen showed me how to write a simple rule file. Dave Date: Sat, 3 Nov 2012 10:36:23 +0100 From: bullt1...@gmail.com To: oselas@c

Re: [oselas] install_alternative

2012-11-02 Thread Dave Festing
ITY,optional) @$(call install_fixup, daves_rootfs,SECTION,base) @$(call install_fixup, daves_rootfs,AUTHOR,"Dave Festing ") @$(call install_fixup, daves_rootfs,DESCRIPTION,missing) # my install_alternative files . . . ifdef PTXCONF_DAVES_ROOTFS_MY_HOME_FILES_AND_D

[oselas] install_alternative

2012-11-02 Thread Dave Festing
Can install_alternative be used to install a directory or multiple files (at once) rather than an individual file? For example, I have this in my daves_rootfs.make file: ifdef PTXCONF_DAVES_ROOTFS_TEST_PHP @$(call install_alternative, daves_rootfs, 0, 0, 0755, /home/test.php) endif Rathe

Re: [oselas] Defer third quarter release of the Mini2440 BSP

2012-09-19 Thread Dave Festing
> Juergen, I am quite happy you leaving it until then. Sounds an exciting development. Mehmet, I will write a HowTo document that should help reduce the risk of a heart attack! Around mid-October. Cheers, Dave

Re: [oselas] Mini2440 Board Problems with Xorg while compilation

2012-08-26 Thread Dave Festing
Maybe, fontutil is another program like fakeroot that you have to install manually. http://ie.archive.ubuntu.com/ftp.frugalware.org/pub/frugalware/ frugalware-current/source/x11/font-util/ Just a suggestion as I haven't tried to build xorg. Good luck!

Re: [oselas] msmtp Rules file

2012-08-13 Thread Dave Festing
> > @$call install_copy, msmtp, 0, 0, 0755, $(MSMTP_DIR)/src/msmtp, /dev/null) > > This would copy the file in "$(MSMTP_DIR)/src/msmtp" into target's > 'dev/null'. > I think it is not what you intend to do ;) Correct, I changed /dev/null to /usr/bin/msmtp > BTW: Many autotools based packages

Re: [oselas] msmtp Rules file

2012-08-13 Thread Dave Festing
Oops, msmtp has not been installed in root/usr but in build-target/msmtp-1.4.28/src I'll try again, so ignore my incorrect changes to @$call install_copy . . .

Re: [oselas] msmtp Rules file

2012-08-13 Thread Dave Festing
>Juergen, I spent about an hour on Google and reading documentation on sourceforge trying to figure out how one accesses files at: > ptxdist: enter URL of basedir.: http://downloads.sourceforge.net/project/msmtp/msmtp/1.4.28 I noticed that when you click on the above link that I end up a

[oselas] msmtp Rules file

2012-08-12 Thread Dave Festing
Trying to make a rules file for msmtp and I am stopped at . I can not find any archives that don't have a /download after the file name and putting <.tar.bz2/download> in the MSMTP_SUFFIX line doesn't work. msmtp is not in the pengutronix.de/software/ptxdist/temporary-src directory either. Any

Re: [oselas] Mini2440BSP-2012-06.0 fakeroot

2012-08-02 Thread Dave Festing
Entering again . . . The symlink to PTXdist-2012.06.0 behaved the same. The puzzling thing is I was able to do one successful build so PTX must have found a correct version to use. I'll work away quietly, noting that the patch will have to be re-applied . . . if I start over.

Re: [oselas] Mini2440BSP-2012-06.0 fakeroot

2012-08-02 Thread Dave Festing
SORRY guys! Classic error (well for me) I did not actually remove PTXdist-2011.11.0 when I said I did. I have not removed anything yet, so will just get rid of PTXdist-2011.11.0 or make a symlink like has been described so many times before. Exit . . . Dave

Re: [oselas] Mini2440BSP-2012-06.0 fakeroot

2012-08-02 Thread Dave Festing
> Or switched to a new version of ptxdist without recompiling everything. - I cleaned everything to do with PTXdist off the machine - installed PTXdist 2011.11.0 - built the toolchain - removed PTXdist 2011.11.0 (paranoid!) - installed PTXdist 2012.06.0 - built mini2440BSP-2012.06.0 - applied the

[oselas] Mini2440BSP-2012-06.0 fakeroot

2012-08-02 Thread Dave Festing
Got all the way through to a successful image and then went back and changed a few things in ptxdist menuconfig. Started off re-building glibc (because I ticked the timezone stuff?) and ended with this error: lib - /opt/OSELAS.Toolchain-2011.11.0/arm-v4t-linux-gnueabi/gcc-4.6.2-glibc-2.14.1- binu

Re: [oselas] echo and cat problems

2012-07-24 Thread Dave Festing
Juergen Beisert writes: > > Hi Dave, > > Dave Festing wrote: > > I can echo and cat /dev/ttyACM0 on my desktop installation of Ubuntu > > 10.02TLS, but there must be a different way of doing in on the mini2440! > > > > Doing cat /dev/ttyACMO just results in

[oselas] echo and cat problems

2012-07-19 Thread Dave Festing
I can echo and cat /dev/ttyACM0 on my desktop installation of Ubuntu 10.02TLS, but there must be a different way of doing in on the mini2440! Doing cat /dev/ttyACMO just results in a long period of "thinking" before I hit CTRL C to get back to the prompt. The command: adduser -G root dialout ju

Re: [oselas] Build problems with mini2440 BSP

2012-07-16 Thread dave festing
Karim, Attached is a script for building an older version of PHP5. Also, you will need to change the script to the latest Pengutronix toolchain, if that is what you are using. Cheers, Dave php5-compile.sh Description: application/shellscript

Re: [oselas] ptxdist newpackage src-make-prog

2012-07-02 Thread Dave Festing
Juergen, If I used the ptxdist drop nanocom compile I would get this: davef@davef-laptop:~/Pengutronix12$ ptxdist go --- target: nanocom.compile --- make[1]: Entering directory `/home/davef/Pengutronix12/platform-mini2440/ build-target/nanocom-1.0' rm -rf

Re: [oselas] ptxdist newpackage src-make-prog

2012-07-01 Thread Dave Festing
Juergen, Thought I'd go with the second method. Just to confirm: mkdir -p patches/nancom-1.0 for me is in $(PTXDIST_WORKSPACE)/patches/ (= BSP) /usr/local/lib/ptxdist-2011.12.0 and because it is owned by root sudo was required. However, I don't understand what this step is doing: echo dummy

Re: [oselas] ptxdist newpackage src-make-proghen

2012-07-01 Thread Dave Festing
Juergen, Thanks for your usual detailed procedures, this time with two options! I'll them both a trial-run. Cheers, Dave

Re: [oselas] ptxdist newpackage src-make-prog

2012-07-01 Thread Dave Festing
I should add that there are 3 .c files that make up the source for Nanocom. I suspect it might be because it doesn't know this little fact. BTW, a trail run with the default Hello world example works fine.

[oselas] ptxdist newpackage src-make-proghen

2012-07-01 Thread Dave Festing
As minicom running on a 3.5" mini2440 requires a very small font (4*6) I ticked the nanocom box. It runs fine but I would like to change it's display to fit better on my small screen. So, I thought why not do a ptxdist newpackage src-make-prog called mycom. Project sets up OK, but will not compi

Re: [oselas] udevd waiting for devices . . . failed

2012-06-11 Thread Dave Festing
Hang on a minute . . . I must not be looking for this in the correct manner. There is no devtmpfs seen in the host filesystem as well. Also, can't find devtmpfs in /proc. I am lost! I can see a /home/davef/Pengutronix12/platform-mini2440/build-target/ linux-3.1/include/config/devtmpfs that has

Re: [oselas] udevd waiting for devices . . . failed

2012-06-11 Thread Dave Festing
And DEVTMPFS_MOUNT=y

Re: [oselas] udevd waiting for devices . . . failed

2012-06-11 Thread Dave Festing
There is no /dev/tmpfs on the target. Had a look in the kernelconfig and DEVTMPFS=y What next? Thanks,Dave

[oselas] udevd waiting for devices . . . failed

2012-06-10 Thread Dave Festing
Noticed this seems to happen about 50% of the time since I have been back on NFS. On SDcard it only pauses for about 3 seconds. So, in /etc/init.d/udev I changed /sbin/udevadm settle ---timeout=20 I now notice, using NFS, that it takes about 10 seconds for the message to come up, so I guess it

Re: [oselas] NFS on the mini2440

2012-05-18 Thread Dave Festing
Juergen, > Sure. The word "network" in the "Network File System" implies a working > network... :) I'll add that to my growing list of helpful reminders! I understood the comment in /evn/config "use 'none' if you want to skip kernel autoconfiguration" to mean that one was skipping autoconfigu

Re: [oselas] Missing autconf

2012-05-18 Thread Dave Festing
Yah Mk writes: > > Untill today I was working with ptxdist-2011.11.0. > No idea why I decided to upgrade :) > What I have done: > > 1. installed ptxdist-2012.02.2 > 2. extracted OSELAS.Toolchain-2011.11.1 >ptxdist select ptxconfigs/arm- etc. >ptxdist go >everthings was fine, bu

Re: [oselas] NFS on the mini2440

2012-05-17 Thread Dave Festing
Got tftp working properly. Let's say that something was not configured properly. Then it stopped at trying to load the root filesystem. Just by a stroke of luck I tried commenting out: ip=none and it now WORKS. Recall, that ip=none was enabled to allow the mini2440 to boot up without an eth

Re: [oselas] NFS on the mini2440

2012-05-17 Thread Dave Festing
Juergen, But, I am just trying to follow the manual. If I load the kernel by tftp it takes about 5 minutes . . . the SD card method is much faster. On re-reading my procedure for doing back about the middle of last year I see that tftp was used for the kernel. I try to work out why this is so s

Re: [oselas] NFS on the mini2440

2012-05-17 Thread Dave Festing
Any hint about this error: Hit any key to stop autoboot: 1 phy0: Link is up - 100/Full Filename './uImage-mini2440'. NFS failed: Permission denied Looked through most of the barebox source code and only found one mention of "nfs". So, I can't see where the error message is generated. I can tf

Re: [oselas] NFS on the mini2440

2012-05-14 Thread Dave Festing
> $ ptxdist menuconfig barebox > [*] Networking Support ---> > [ ] nfs support > > If you enable this entry, Barebox also "understands" the 'nfs' command to > load > the kernel via NFS protocol. > > A common way to run your target completely via network is to use the TFTP > pro

[oselas] NFS on the mini2440

2012-05-14 Thread Dave Festing
Trying to set up NFS on another machine and have hit a problem: ... # autoboot settings # can be either 'tftp', 'nfs', 'nand' or 'mmc' kernel_loc=nfs # can be either 'net', 'nand', 'initrd' or 'mmc' rootfs_loc=net running /env/bin/init... Hit any key to stop autoboot: 0 Unknown command 'nf

[oselas] ptxdist extract kernel

2012-04-25 Thread Dave Festing
I have read that this command will do the following: - clean - extract - patch Just curious if anything else happens, for example to the .config file. Mine seemed to be unchanged. Is this expected behaviour? Thanks, Dave

Re: [oselas] error: ‘selected_ptxconfig’ file is missing

2012-04-24 Thread Dave Festing
Seeing as you have the latest toolchain, why not download 2011.12.0 or one of the latest BSPs? I had some issues with pxtdist 2011.11.0 that I could not confidently pass on as a suggestion.

Re: [oselas] ptxdist drop (?)

2012-04-09 Thread Dave Festing
Juergen Beisert > > But I didn't add the .in and the .make files into the rules directory! > You didn't add them??? Who else? Has someone hacked your host? > I'm innocent! > (except for mini2440-demo.in, qml-demo.make and qt4-demo.make) Let's try again . . . when one calls ptxdist newpackage

Re: [oselas] ptxdist drop (?)

2012-04-09 Thread Dave Festing
> \o/ If you have a proposal how to describe this PTXdist feature, I would be > happy to integrate it into the "How to become a PTXdist guru" manual. Who . . . me? Sure I'll describe the reason for doing this tomorrow. > Since you add this package and its files into your project, you also must

  1   2   3   >