From louigi600 at yahoo.it Wed Jul 10 18:07:19 2013 From: louigi600 at yahoo.it (Davide) Date: Wed, 10 Jul 2013 19:07:19 +0100 (BST) Subject: [ARMedslack] Exagerate XZPDA700 In-Reply-To: <1372155514.46356.YahooMailNeo@web28801.mail.ir2.yahoo.com> References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> <1371193976.31697.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1371214861.65453.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1371910854.63649.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1372155514.46356.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: <1373479639.30946.YahooMailNeo@web28806.mail.ir2.yahoo.com> I got the kernel loading from uSD but then kernel panic because uboot passes wrong root device to kernel. http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet I discovered that I cannot have the serial console if I boot feom uSD so I need some other means of manipulating the u-boot environment from the image before writing it to uSD, or in any case on the uSD before I try to boot. Anyone have an idea hot to fix that ?? Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Jul 11 06:34:07 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 11 Jul 2013 07:34:07 +0100 (BST) Subject: [ARMedslack] Exagerate XZPDA700 In-Reply-To: <1373479639.30946.YahooMailNeo@web28806.mail.ir2.yahoo.com> References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> <1371193976.31697.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1371214861.65453.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1371910854.63649.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1372155514.46356.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1373479639.30946.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: <1373524447.28472.YahooMailNeo@web28803.mail.ir2.yahoo.com> >I got the kernel loading from uSD but then kernel panic because uboot passes wrong root device to kernel. >http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet >I discovered that I cannot have the serial console if I boot feom uSD so I need some other means of manipulating the u-boot environment from the image before writing it to uSD, or in any case on the uSD before I try to >boot. >Anyone have an idea hot to fix that ?? Having a better look at the u-boot environment it appears that it fetches variables from text files present in the boot partition so it's fixed. Last night I was able to boot and get to a login prompt. I had no usb keyboard so all I was able to do was turn it off again. I'll clean up the wiki page asap. Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Thu Jul 11 06:34:07 2013 From: louigi600 at yahoo.it (Davide) Date: Thu, 11 Jul 2013 07:34:07 +0100 (BST) Subject: [ARMedslack] Exagerate XZPDA700 In-Reply-To: <1373479639.30946.YahooMailNeo@web28806.mail.ir2.yahoo.com> References: <20130611204310.D8587778563DF@bmail03.one.com> <20130612143847.ABC8D62505E0C@bmail-n01.one.com> <1371106309.60015.YahooMailNeo@web28803.mail.ir2.yahoo.com> <1371193976.31697.YahooMailNeo@web28804.mail.ir2.yahoo.com> <1371214861.65453.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1371910854.63649.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1372155514.46356.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1373479639.30946.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: <1373524447.28472.YahooMailNeo@web28803.mail.ir2.yahoo.com> >I got the kernel loading from uSD but then kernel panic because uboot passes wrong root device to kernel. >http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet >I discovered that I cannot have the serial console if I boot feom uSD so I need some other means of manipulating the u-boot environment from the image before writing it to uSD, or in any case on the uSD before I try to >boot. >Anyone have an idea hot to fix that ?? Having a better look at the u-boot environment it appears that it fetches variables from text files present in the boot partition so it's fixed. Last night I was able to boot and get to a login prompt. I had no usb keyboard so all I was able to do was turn it off again. I'll clean up the wiki page asap. Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Jul 12 15:01:04 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 12 Jul 2013 16:01:04 +0100 (BST) Subject: [ARMedslack] miniroot 14 and current: vi is broken In-Reply-To: References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: <1373641264.22537.YahooMailNeo@web28801.mail.ir2.yahoo.com> >> Well actually on my live slackware 14 (x86)? vi is a link to elvis >> >> Although both are installed, by default vi is linked to elvis (and it's >> not something I did manually). looking at the sizes I cannot but agree >> that on the miniroot vim is just eating up space (just guessing that the >> arm packages will me more or less the same size) and on top of that >> there's 120Mb of dependencies to use it ! >Since (if selected) elvis is installed first (due to being in series 'a'), >it sets up a symlink in the doinst.sh script. >If vim is installed, its doinst.sh script checks for the presence of the >'vi' symlink, and if not present, will symlink 'vi' to 'vim'. >root at pepa:~/ac/source/a/elvis# head -n2 /var/log/scripts/elvis-2.2-arm-2 >( cd usr/bin ; rm -rf vi ) >( cd usr/bin ; ln -sf elvis vi ) >root at pepa:~/ac/source/a/elvis# I noticed that vi? in the miniroot slackware ARM 14 is still vim and lacking libs to make it functional. Elvis is not installed in the miniroot. Ok you can put it right pretty fast but it can be annoying if on the target device there is no means to get an extra package in apart from manipulating the flash. Ciao David -------------- next part -------------- An HTML attachment was scrubbed... URL: From huckfinn1963 at comcast.net Fri Jul 12 17:39:07 2013 From: huckfinn1963 at comcast.net (Dennis) Date: Fri, 12 Jul 2013 12:39:07 -0500 Subject: [ARMedslack] armedslack on android phone? Message-ID: Hello all ??? I have a motorola bionic phone with android JB. With it I have a webdock, which is basically a hdmi monitor with a usb mouse and keyboard.? I use this fairly often and what I really miss is running linux as android is a? modified version and just doesn't have the same look, feel, and functionality as a full linux system.? I run slackware 14 on my home system, and when I found out slackware had this group I joined up. So far it looks like the rasp pi and simular computers are the target. Just wondering if anyone has ventured into the android phone area?? I'm not sure if a dual boot would be possible?? Or if it would have to run under the android shell as other linux distro's do.? I haven't done much programming for a long time, but I do continue to use and play around with my linux machine at home.? Been a slackware fan since 1992 or so and after trying some of the other distro's I found I prefer slackware still. Dual boot would be prefered, and I have found that the drivers for the phone are available thru android open source so just maybe this would be workable. ???????? I'm also looking to get a small computer like one of usb sticks I've seen to put the web on the TV, and am looking for any advice as to which would be the best for slackware/android combo. thanks ????????????? Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From gorecki at fastguys.net Sat Jul 13 13:30:09 2013 From: gorecki at fastguys.net (Brian L Gorecki) Date: Sat, 13 Jul 2013 09:30:09 -0400 Subject: [ARMedslack] armedslack on android phone? In-Reply-To: References: Message-ID: <000601ce7fcd$187ef600$497ce200$@net> The most straight forward answer would be no, the arm architecture used in that phone isn?t supported ?out of the box?. However, with some work, kernel builds and patience probably can be done. See http://arm.slackware.com/supportedplatforms/ for a starting point. I?ve had the same thoughts for an old Motorola Q I have but so far haven?t deemed it worth the effort. From: ARMedslack [mailto:armedslack-bounces at lists.armedslack.org] On Behalf Of Dennis Sent: Friday, July 12, 2013 1:39 PM To: armedslack at lists.armedslack.org Subject: [ARMedslack] armedslack on android phone? Hello all I have a motorola bionic phone with android JB. With it I have a webdock, which is basically a hdmi monitor with a usb mouse and keyboard. I use this fairly often and what I really miss is running linux as android is a modified version and just doesn't have the same look, feel, and functionality as a full linux system. I run slackware 14 on my home system, and when I found out slackware had this group I joined up. So far it looks like the rasp pi and simular computers are the target. Just wondering if anyone has ventured into the android phone area? I'm not sure if a dual boot would be possible? Or if it would have to run under the android shell as other linux distro's do. I haven't done much programming for a long time, but I do continue to use and play around with my linux machine at home. Been a slackware fan since 1992 or so and after trying some of the other distro's I found I prefer slackware still. Dual boot would be prefered, and I have found that the drivers for the phone are available thru android open source so just maybe this would be workable. I'm also looking to get a small computer like one of usb sticks I've seen to put the web on the TV, and am looking for any advice as to which would be the best for slackware/android combo. thanks Dennis -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Sun Jul 14 09:22:49 2013 From: louigi600 at yahoo.it (Davide) Date: Sun, 14 Jul 2013 10:22:49 +0100 (BST) Subject: [ARMedslack] armedslack on android phone? In-Reply-To: <000601ce7fcd$187ef600$497ce200$@net> References: <000601ce7fcd$187ef600$497ce200$@net> Message-ID: <1373793769.24005.YahooMailNeo@web28805.mail.ir2.yahoo.com> If the phone is an A1x based SOC there's chance that you can get started really quickly by reusing info on how I got Slackware arm on my XZPAD700 tables (that is a A13 based SOC). There's still work to do like the touchscreen and figuring out what kind of X server will work (probably a frame-buffer one) .... but it's booting? and the frambuffer console is working. The documentation has not yet made it to the non officially supported platform list but I've documented my doings on http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet. I've also a self sufficient? image builder that I've tarballed into 63Mb but have no place to put the image on. This new image builder replaces the script I've put on docs.slackware.com and feautres dialog menus for choosing things like target soc,kernel,partition sizes and root image tarball. Stuart: what do you think about adding it to the list along with the AC100,? Pandora and Pi ? Ciao David ________________________________ Da: Brian L Gorecki A: 'Slackware ARM port' Inviato: Sabato 13 Luglio 2013 15:30 Oggetto: Re: [ARMedslack] armedslack on android phone? The most straight forward answer would be no, the arm architecture used in that phone isn?t supported ?out of the box?.? However, with some work, kernel builds and patience probably can be done.? See http://arm.slackware.com/supportedplatforms/ for a starting point.? I?ve had the same thoughts for an old Motorola Q I have but ?so far haven?t deemed it worth the effort. ? ? ? From:ARMedslack [mailto:armedslack-bounces at lists.armedslack.org] On Behalf Of Dennis Sent: Friday, July 12, 2013 1:39 PM To: armedslack at lists.armedslack.org Subject: [ARMedslack] armedslack on android phone? ? Hello all ??? I have a motorola bionic phone with android JB. With it I have a webdock, which is basically a hdmi monitor with a usb mouse and keyboard.? I use this fairly often and what I really miss is running linux as android is a? modified version and just doesn't have the same look, feel, and functionality as a full linux system.? I run slackware 14 on my home system, and when I found out slackware had this group I joined up. So far it looks like the rasp pi and simular computers are the target. Just wondering if anyone has ventured into the android phone area?? I'm not sure if a dual boot would be possible?? Or if it would have to run under the android shell as other linux distro's do.? I haven't done much programming for a long time, but I do continue to use and play around with my linux machine at home.? Been a slackware fan since 1992 or so and after trying some of the other distro's I found I prefer slackware still. Dual boot would be prefered, and I have found that the drivers for the phone are available thru android open source so just maybe this would be workable. ???????? I'm also looking to get a small computer like one of usb sticks I've seen to put the web on the TV, and am looking for any advice as to which would be the best for slackware/android combo. ? thanks ????????????? Dennis ? _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Sun Jul 14 20:45:42 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sun, 14 Jul 2013 21:45:42 +0100 Subject: [ARMedslack] armedslack on android phone? In-Reply-To: <1373793769.24005.YahooMailNeo@web28805.mail.ir2.yahoo.com> References: <000601ce7fcd$187ef600$497ce200$@net> <1373793769.24005.YahooMailNeo@web28805.mail.ir2.yahoo.com> Message-ID: <20130714204542.E3A7BE836A2C4@bmail-n01.one.com> On Jul 14, 2013 10:22 "Davide" wrote: > If the phone is an A1x based SOC there's chance that you can get > started really quickly by reusing info on how I got Slackware arm on > my XZPAD700 tables (that is a A13 based SOC). There's still work to do > like the touchscreen and figuring out what kind of X server will work > (probably a frame-buffer one) .... but it's booting and the frambuffer > console is working. The documentation has not yet made it to the non > officially supported platform list but I've documented my doings on > http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_t > ablet. > > > > > I've also a self sufficient image builder that I've tarballed into > 63Mb but have no place to put the image on. This new image builder > replaces the script I've put on docs.slackware.com and feautres dialog > menus for choosing things like target soc,kernel,partition sizes and > root image tarball. > > > > > Stuart: what do you think about adding it to the list along with the > AC100, Pandora and Pi ? > > > > > Ciao > > David > > > > > > > Da: Brian L Gorecki > A: 'Slackware ARM port' > Inviato: Sabato 13 Luglio 2013 15:30 > Oggetto: Re: [ARMedslack] armedslack on android phone? > > > > > The most straight forward answer would be no, the arm architecture > used in that phone isn?t supported ?out of the box?. However, with > some work, kernel builds and patience probably can be done. See > for a starting point. > I?ve had the same thoughts for an old Motorola Q I have but so far > haven?t deemed it worth the effort. > > > > > > > > From:ARMedslack [mailto:armedslack-bounces at lists.armedslack.org] On > Behalf OfDennis > Sent: Friday, July 12, 2013 1:39 PM > To: armedslack at lists.armedslack.org > Subject: [ARMedslack] armedslack on android phone? > > > > Hello all > > I have a motorola bionic phone with android JB. With it I have a > webdock, which is > > basically a hdmi monitor with a usb mouse and keyboard. I use this > fairly often and > > what I really miss is running linux as android is a modified version > and just doesn't > > have the same look, feel, and functionality as a full linux system. I > run slackware 14 on my home system, and when I found out slackware had > this group I joined up. > > So far it looks like the rasp pi and simular computers are the target. > Just wondering > > if anyone has ventured into the android phone area? I'm not sure if a > dual boot would be possible? Or if it would have to run under the > android shell as other linux distro's do. I haven't done much > programming for a long time, but I do continue to use and play around > with my linux machine at home. Been a slackware fan since 1992 or so > and after trying some of the other distro's I found I prefer slackware > still. > > Dual boot would be prefered, and I have found that the drivers for the > phone are available thru android open source so just maybe this would > be workable. > > I'm also looking to get a small computer like one of usb sticks I've > seen to put the web on the TV, and am looking for any advice as to > which would be the best for slackware/android combo. > > > > thanks > > Dennis > > > > _______________________________________________ > ARMedslack mailing list > > > > Slackware ARM is very generic and will run on an spectacular amount of > devices. How you get it on to an unsupported device is the rub. I > doubt that you can dual boot in the conventional sense as ARM devices > don't use LILO as your desktop will. In fact most ARM systems boot > differently, some use uboot, some yaffs. (Slackware ARM uses both > inird and uboot). Some will use a propitiatory procedure that can only > be guessed at. > You will need a custom kernel compiled against your arch, you cant > just use a slackware ARM kernel and expect it to work, it won't. > Your open source drivers will have been compiled for android and will > use the bionic libararys, Slackware will require that you recompile > the drivers for glib. > You could do this if you are prepared to put in the time, and fail, > stomp your feet, try again until you succeed. > Good luck! -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Jul 15 14:21:30 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 15 Jul 2013 15:21:30 +0100 (BST) Subject: [ARMedslack] miniroot 14 and current: vi is broken In-Reply-To: <1373641264.22537.YahooMailNeo@web28801.mail.ir2.yahoo.com> References: <1366037024.41941.YahooMailNeo@web28801.mail.ir2.yahoo.com> <1366125626.37266.YahooMailNeo@web28802.mail.ir2.yahoo.com> <1373641264.22537.YahooMailNeo@web28801.mail.ir2.yahoo.com> Message-ID: > I noticed that vi? in the miniroot slackware ARM 14 is still vim and > lacking libs to make it functional. Elvis is not installed in the > miniroot. Ok you can put it right pretty fast but it can be annoying if > on the target device there is no means to get an extra package in apart > from manipulating the flash. I didn't fix 14.0. I'll fix it before the next batch goes out. -- Stuart Winter Slackware ARM: http://arm.slackware.com From m-lists at biscuit.org.uk Mon Jul 15 14:26:52 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 15 Jul 2013 15:26:52 +0100 (BST) Subject: [ARMedslack] armedslack on android phone? In-Reply-To: <20130714204542.E3A7BE836A2C4@bmail-n01.one.com> References: <000601ce7fcd$187ef600$497ce200$@net> <1373793769.24005.YahooMailNeo@web28805.mail.ir2.yahoo.com> <20130714204542.E3A7BE836A2C4@bmail-n01.one.com> Message-ID: > > Stuart: what do you think about adding it to the list along with the > > AC100, Pandora and Pi ? How's about the 3rd party device support page is moved on to the ARM section of docs.slackware.com, and I change the link on http://arm.slackware.com to point to it. I don't think I need to be the custodian of the support matrix. If you want to go ahead and create the page on docs.slackware.com, go ahead and let me know once it's done. From stanley at stanleygarvey.com Mon Jul 15 23:58:59 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Tue, 16 Jul 2013 00:58:59 +0100 Subject: [ARMedslack] Kernel 2.10 and raspberry pi Message-ID: <20130715235859.CE5E66C598584@bmail06.one.com> Hi, just been to kernel.org to see if the raspberry pi is supported. I see no support for the device in any kernel previous to 3.10.1 which includes support for the BCM2835. I find this odd. I would have thought that patches would have been submitted and merged in the the kernel tree. We still got super H Dreamcast code in there so why no Raspberry pi? Work is still being done on 3.6.11 at raspberry pi github. Work stopped last year on 3.2.27, so why are the patches not in kernel.org? I don't get this. I could post this to Raspberry pi, however my feeling is that I will not get a definitive answer. Perhaps I am misunderstanding how the process works. Please enlighten me. -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Tue Jul 16 06:52:22 2013 From: louigi600 at yahoo.it (Davide) Date: Tue, 16 Jul 2013 07:52:22 +0100 (BST) Subject: [ARMedslack] armedslack on android phone? In-Reply-To: References: <000601ce7fcd$187ef600$497ce200$@net> <1373793769.24005.YahooMailNeo@web28805.mail.ir2.yahoo.com> <20130714204542.E3A7BE836A2C4@bmail-n01.one.com> Message-ID: <1373957542.70954.YahooMailNeo@web28806.mail.ir2.yahoo.com> >> > Stuart: what do you think about adding it to the list along with the >> > AC100, Pandora and Pi ? >How's about the 3rd party device support page is moved on to the ARM >section of docs.slackware.com, and I change the link on >http://arm.slackware.com to point to it. >I don't think I need to be the custodian of the support matrix.? If you >want to go ahead and create the page on docs.slackware.com, go ahead and >let me know once it's done. That's exactly what I was trying to say. Different story if you want me to add it to the non officially supported platforms section on the? http://arm.slackware.com/supportedplatforms/ page. I've Slackware ARM booting on a AL-A13-RT713 board that came inside a tablet (XZPAD700) and I've documented my doings from hacking the info out of it to creating a MicroSD image for booting the Slackware miniroot and it's already all on http://docs.slackware.com/howtos:hardware:arm:hacking_the_xzpad700_7_tablet I've also a tarball that contains all that is necessary to create bootable slackware miniroot for almost any A1x device that is currently supported by linux-sunxi, but I've no place to share it with anybody that may be intrested. David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Tue Jul 16 13:23:37 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 16 Jul 2013 14:23:37 +0100 (BST) Subject: [ARMedslack] armedslack on android phone? In-Reply-To: <1373957542.70954.YahooMailNeo@web28806.mail.ir2.yahoo.com> References: <000601ce7fcd$187ef600$497ce200$@net> <1373793769.24005.YahooMailNeo@web28805.mail.ir2.yahoo.com> <20130714204542.E3A7BE836A2C4@bmail-n01.one.com> <1373957542.70954.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: > >http://arm.slackware.com to point to it. > >I don't think I need to be the custodian of the support matrix.? If you > >want to go ahead and create the page on docs.slackware.com, go ahead and > >let me know once it's done. > > That's exactly what I was trying to say. Different story if you want me > to add it to the non officially supported platforms section on the? > http://arm.slackware.com/supportedplatforms/ page. I've moved the community platforms and linked it from that page, so the community can update the list. -- Stuart Winter Slackware ARM: http://arm.slackware.com From louigi600 at yahoo.it Wed Jul 17 05:24:41 2013 From: louigi600 at yahoo.it (Davide) Date: Wed, 17 Jul 2013 06:24:41 +0100 (BST) Subject: [ARMedslack] armedslack on android phone? In-Reply-To: References: <000601ce7fcd$187ef600$497ce200$@net> <1373793769.24005.YahooMailNeo@web28805.mail.ir2.yahoo.com> <20130714204542.E3A7BE836A2C4@bmail-n01.one.com> <1373957542.70954.YahooMailNeo@web28806.mail.ir2.yahoo.com> Message-ID: <1374038681.61200.YahooMailNeo@web28806.mail.ir2.yahoo.com> >>>http://arm.slackware.com to point to it. >>>I don't think I need to be the custodian of the support matrix.? If you >>>want to go ahead and create the page on docs.slackware.com, go ahead and >>>let me know once it's done. >> That's exactly what I was trying to say. Different story if you want me >> to add it to the non officially supported platforms section on the? >> http://arm.slackware.com/supportedplatforms/ page. >I've moved the community platforms and linked it from that page, so the >community can update the list. I've added the XZPAD700 to that Thanks Stuart Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Fri Jul 19 19:24:26 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 19 Jul 2013 20:24:26 +0100 (BST) Subject: [ARMedslack] Kernel 2.10 and raspberry pi In-Reply-To: <20130715235859.CE5E66C598584@bmail06.one.com> References: <20130715235859.CE5E66C598584@bmail06.one.com> Message-ID: > just been to kernel.org to see if the raspberry pi is supported. I see > no support for the device in any kernel previous to 3.10.1 which > includes support for the BCM2835. I find this odd. I would have thought > that patches would have been submitted and merged in the the kernel > tree. We still got super H Dreamcast code in there so why no Raspberry > pi? Work is still being done on 3.6.11 at raspberry pi github. Work > stopped last year on 3.2.27, so why are the patches not in kernel.org? > I don't get this. I could post this to Raspberry pi, however my feeling > is that I will not get a definitive answer. Perhaps I am > misunderstanding how the process works. Please enlighten me. I don't know, but my question is - does it matter? If the support's in 3.10.1 then what's the issue? Usually the developers keep the code in a particular branch until they get it stable (which usually takes months to achieve - which if they were to have it in a moving-target branch, would mean that their code would need to be refactored). Once it's stable, they can forward port it into a newer release -- the core of the code is tested but it just needs to be shuffled about a bit to fit into the new tree. I plan in late August to look at 3.10 for Slackware ARM, as it involves a massive upheval for which which I do not have the time now; but if the RPi support is there in 3.10.1, you might as well use the 3.10 kernel. -- Stuart Winter Slackware ARM: http://arm.slackware.com From ottavio2006-usenet2012 at yahoo.com Fri Jul 19 19:15:16 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Fri, 19 Jul 2013 20:15:16 +0100 Subject: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: <20130719133053.GA9965@xs4all.nl> References: <20130719133053.GA9965@xs4all.nl> Message-ID: For whoever is interested. Maybe it's possible to port Slackware to the A20. Luke Leighton is already producing some prototypes. I've asked on the arm-netbook list if anybody is interested in seeing Slackware running on it. If that rings any bells, please give a shout. I might buy one myself if/when the device is usable. My budget is limited as I'm out ot work. ---------- Forwarded message ---------- From: "Antony Antony" Date: Jul 19, 2013 2:31 PM Subject: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) To: this is an interesting news item, though my prefeence is a debian. -antony ---------- Forwarded message ---------- Date: Thu, 18 Jul 2013 18:12:35 From: Hans de Goede To: linux-sunxi at googlegroups.com, Fedora ARM , Development discussions related to Fedora Subject: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support Hi All, I'm very happy to announce the first release (r1) of my Fedora 19 ARM remix images for Allwinner A10, A10s, A13 and A20 based devices. This release is based on the official Fedora 19 Final for ARM images, with u-boot and kernel(s) from the linux-sunxi project: http://linux-sunxi.org/ Besides all the goodies from Fedora-19, this release also contains the following new items on the Allwinner / sunxi front: -Support for the new dual core A20 soc (tested with cubieboard2), this is based on forward porting the core machine code + various drivers from allwinners 3.3 kernel source dump to the sunxi-3.4 sources. The following has been ported / is supported: -uarts -mmc controllers -ehci and ohci usb controllers (usb controllers 1 and 2, controller 0 is an otg controller and is not supported yet. -video output block (hdmi, vga, lcd, composite out) -i2c controllers -axp pmic including cpu voltage scaling -rtc -sound: analog in/out, hdmi audio, spdif out (spdif untested) -ethernet controller (emac) -sata controller Note any functional blocks in the SOC which are not explictly listed as supported above are not supported atm -Support for a couple of new boards (38 boards in total now) You can download it here: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r1.img.xz sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a It is important to read the README, the image standard comes without u-boot pre-loaded since u-boot is board specific. The image includes a user-friendly simple script to install the right u-boot for your board, but if you simply xzcat the image to an sdcard, and then boot your device with the sdcard, things will *not* work. See the README for a list of currently supported boards. Known Issues: -Many boards don't have an rtc (A10 and A20 have a builtin one), or at least no battery backup for it, resulting in the date + time being wrong. -If the date is of by more then a couple of months, "yum update" won't work because certificate validation fails for the https connection yum tries to make. So if yum fails to get its repodata first check (and fix) your date -The regular (host not otg) usb-port on A10s based boards can be a bit quirky. It is best to plug in a hub even when using only one device, otherwise the device may not be recognized. If this happens, after adding a hub, often a power-cycle is needed too. -The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README ----------------------------------------------------------------- Quickstart guide ---------------- 1) Insert an sdcard, note any data on the card will be destroyed! 2) Make sure the card is not mounted, run "mount" and if the card shows up in the output umount its partitions 3) Write the img file to the card, ie as root do: xzcat Fedora-19-a10-armhfp-r1.img.xz > /dev/mmcblk0 sync 4) The card is not yet ready for use! Since the A10 u-boot is board specific, the image comes without any uboot install, follow the next steps to install the right u-boot for your board 5) Remove the card, and re-insert it. The uboot partition should get automatically mounted, if not mount it manually, 6) As root (or through sudo) run: /select-board.sh, ie: sudo /run/media/hans/uboot/select-board.sh If you've dialog installed the select-board.sh script will prompt for your board. If you don't have dialog installed, it will print the list of supported boards. Lookup your board and re-run the script with the shortname for your board as argument, ie: sudo /run/media/hans/uboot/select-board.sh mk802 7) umount the uboot and rootfs partitions, ie: umount /run/media/hans/uboot umount /run/media/hans/rootfs 8) Your sdcard is now ready for use 9) *Before* powering up your A10 device connect it to an hdmi or dvi monitor 10) When first booting from the sdcard inserted Fedora will automatically reboot once, this is part of the process to resize the root partition to fill the entire sdcard and is normal behavior. 11) After the automatic reboot Fedora will start with the initial-setup wizard: 11a) Configure networking, note: * If you've an A10 board with wired ethernet and you want to use dhcp you don't need to do anything. * If you've an A20 board, your ethernet will have a random mac-address, so if you want to configure a static ip-address and want it to stick across reboots, go to the ethernet-tab, select the mac-address field and delete its contents, so that the static ip address you're configuring does not get tied to the random mac-address. 11b) Setup the time zone 11c) Set a root password 11d) Create a user 12) Log in as the just created user 13) Enjoy Fedora on your A10 device Supported Devices: ------------------ Fedora 19 ARM for Allwinner A10 has been tested with the following devices: * A13-OLinuXino-MICRO (Olimex) * Auxtek T003 hdmi tv stick * Auxtek T004 hdmi tv stick * BA10 TV Box * Cubieboard development board 1024 MB RAM * Cubieboard2 (A20) development board * Gooseberry development board * Mele A1000G/A2000G 1024 MB RAM * Mini-X 1024 MB RAM * mk802 (with female mini hdmi) 512 MB RAM * mk802 with A10s (s with a circle around it on the barcode label) * mk802ii (with male normal hdmi) 1024 MB RAM * r7 hdmi tv stick * UHost U1A hdmi tv stick * Wobo i5 TV Box Fedora 19 ARM should also work on the following devices: * A10 tablet sold under various names (whitelabel) * A13 tablet sold under various names (whitelabel) * A10s-OLinuXino-MICRO (Olimex) * A13-OLinuXino (Olimex) * A20-OLinuXino-MICRO (Olimex) * Coby MID7042 tablet * Coby MID8042 tablet * Coby MID9742 tablet * Cubieboard development board 512 MB RAM * DNS AirTab M82 tablet * EOMA68 A10 CPU card * H6 netbook * Hackberry development board * Hyundai a7hd tablet * iNet-97F Rev.2 (and clones) tablet * Mele A1000/A2000 512 MB RAM * Mele A3700 * Mini-X 512 MB RAM * mk802 (with female mini hdmi) 1024 MB RAM * pcDuino development board * Point of View ProTab 2 IPS 9" tablet * Point of View ProTab 2 IPS tablet with 3g * XZPAD700 7" tablet Configuring the display output ------------------------------ Multiple video outputs at the same time are not supported. By default hdmi output with EDID is used for all devices, except for tablets/netbooks where the default output is the lcd. The default hdmi output with EDID will get the native resolution of your TV / monitor and use that. Note that in order for this to work your TV / monitor must be connected *and turned on*, before booting your device. The output resolution can be configured with the disp.screen0_output_mode kernel cmdline value, which can be found in the extrargs part of uEnv.txt in the uboot partition. The default uEnv.txt contains the following value: disp.screen0_output_mode=EDID:1280x720p60 This means try to use EDID and if no valid EDID info is found fallback to 1280x720p60. The used output can be changed by adding disp.screen0_output_type=X to the extraargs in uEnv.txt. With X being one of: 0:none; 1:lcd; 2:tv; 3:hdmi; 4:vga Some per display type notes: -lcd outputs: Hardcoded to the native mode, disp.screen0_output_mode is ignored -tv: For the cvbs output disp.screen0_output_mode must be set to one of the following: pal, pal-svideo, ntsc, ntsc-svideo, pal-m, pal-m-svideo, pal-nc, pal-nc-svideo. Note the -svideo variants should only be used on boards with an svideo connector, for composite out use the regular variants, ie: disp.screen0_output_type=2 disp.screen0_output_mode=pal -hdmi: To override the EDID detected mode, drop the "EDID:" from the disp.screen0_output_mode value and set it to the desired mode, ie: disp.screen0_output_type=3 disp.screen0_output_mode=1360x768p60 -vga: Does not support EDID, "EDID:" must be removed from the disp.screen0_output_mode value otherwise it will be ignored. interlaced progressive and refreshrate settings specified are ignored, each resolution has hardcoded values for these. Example usage: disp.screen0_output_type=4 disp.screen0_output_mode=1024x768 USB controller caveats ---------------------- The OTG USB controller in host mode only supports a limited number of devices, plugging in a hub + mouse + keyboard typically will make either the mouse or keyboard not work. This is a hardware limitation which we will likely not be able to work around. On tv-sticks and top-set boxes, simply avoid the otg connector, instead use a hub in a regular host usb connector. Note on the mini-x the otg / host marking is not always correct. If things don't work try using the OTG connector instead! On tablets and the gooseberry unfortunately only the otg connector is available. One solution there is using a single usb-device which is both a keyboard and a mouse at the same time. IE the receiver for logitech wireless desktop sets. Supported hardware components / features: ----------------------------------------- Fedora 19 ARM for Allwinner A10 supports the following components: * CPU + PMU + RAM * Serial ports * MMC cards * Internal NAND storage (*) * Framebuffer on lcd / vga / hdmi / composite video * Sound both analog out and over hdmi * OTG USB controller (*) * Both standard USB host controllers * Wifi * Wired Ethernet * SATA * IR (untested at this time) (*) *) Not supported on A20, the A20 support in the Fedora 19 A10 images is new, and as such the driver code for these has not been forward-ported from the Allwinner source dump to the sunxi-3.4 kernel the Fedora 19 A10 images use yet. Unsupported hardware components: -------------------------------- The following components require various proprietary blobs to be used, and as such are not supported in the Fedora images. The kernel drivers for them are present (usually as modules) (*), so if you add the necessary blobs you might get these to work: * Mali 400 GPU * Cedar hardware video & audio decoding and encoding engine * G2D 2d engine *) Except for the A20 Differences from stock Fedora ----------------------------- * Since the A10 is not a very powerful soc some services which are enabled by default on Fedora are disabled in the image, see build-image.sh for a list. * No plymouth: we log to a serial console for debugging so no pretty splash. Also we don't use an initrd, so removing the console=ttyS0,115200 from the extraargs in uEnv.txt will give plymouth, but so late it hardly matters. Rebuilding the Fedora 19 ARM for Allwinner A10 disk image --------------------------------------------------------- Building the Fedora 19 ARM for Allwinner A10 disk image consists of 2 steps 1) Building a uboot.tar.gz and rootfs.tar.gz "overlays", this is done bu the build-boot-root-sh script 2) Combining uboot.tar.gz and rootfs.tar.gz with an official Fedora 19 arm img, this combining is done by the build-image.sh script The a10 image you downloaded is based on Fedora-XFCE-armhfp-19-1-sda.raw These scripts are hosted here: https://github.com/jwrdegoede/sunxi-fedora-scripts.git A copy of the exact versions of these scripts used to build this Fedora A10 image can be found in the scripts directory of the uboot partition, the kernel config used during the build can be found here too. If you want to exactly reproduce this image it is important to use the scripts from the scripts dir of the uboot partition, as the scripts contain GIT tags used during the build to checkout the exact versions to build. The pre-conditions these scripts expect to be met, and the exact usage of them is documented in comments in the top of each script. -- devel mailing list devel at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel _______________________________________________ arm-netbook mailing list arm-netbook at lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook at files.phcomp.co.uk -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Sat Jul 20 06:50:15 2013 From: louigi600 at yahoo.it (Davide) Date: Sat, 20 Jul 2013 07:50:15 +0100 (BST) Subject: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: References: <20130719133053.GA9965@xs4all.nl> Message-ID: <1374303015.63552.YahooMailNeo@web28802.mail.ir2.yahoo.com> My new image builder for the xzpad700 (as soon as I've time to sync it) will prepare images for all the hardware that the fedora currently supports (including the new A20 socs). as a matter of fact I\m using their bootloader and their kernels until I get round to building my own kernel.? Incidently my image builder will let you deploy any distro root filesystem tarball ... but you might need a bit of manual for non slackware root tarballs. Regards David ________________________________ Da: Ottavio Caruso A: ARMedslack at lists.armedslack.org Inviato: Venerd? 19 Luglio 2013 21:15 Oggetto: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) For whoever is interested. Maybe it's possible to port Slackware to the A20. Luke Leighton is already producing some prototypes. I've asked on the arm-netbook list if anybody is interested in seeing Slackware running on it. If that rings any bells, please give a shout. I might buy one myself if/when the device is usable. My budget is limited as I'm out ot work. ---------- Forwarded message ---------- From: "Antony Antony" Date: Jul 19, 2013 2:31 PM Subject: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) To: this is an interesting news item, though my prefeence is a debian. -antony ---------- Forwarded message ---------- Date: Thu, 18 Jul 2013 18:12:35 From: Hans de Goede To: linux-sunxi at googlegroups.com, Fedora ARM , ? ? Development discussions related to Fedora Subject: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, ? ? now with A20 support Hi All, I'm very happy to announce the first release (r1) of my Fedora 19 ARM remix images for Allwinner A10, A10s, A13 and A20 based devices. This release is based on the official Fedora 19 Final for ARM images, with u-boot and kernel(s) from the linux-sunxi project: http://linux-sunxi.org/ Besides all the goodies from Fedora-19, this release also contains the following new items on the Allwinner / sunxi front: -Support for the new dual core A20 soc (tested with cubieboard2), ?this is based on forward porting the core machine code + various ?drivers from allwinners 3.3 kernel source dump to the sunxi-3.4 ?sources. The following has been ported / is supported: ?-uarts ?-mmc controllers ?-ehci and ohci usb controllers (usb controllers 1 and 2, controller ? 0 is an otg controller and is not supported yet. ?-video output block (hdmi, vga, lcd, composite out) ?-i2c controllers ?-axp pmic including cpu voltage scaling ?-rtc ?-sound: analog in/out, hdmi audio, spdif out (spdif untested) ?-ethernet controller (emac) ?-sata controller ?Note any functional blocks in the SOC which are not explictly ?listed as supported above are not supported atm -Support for a couple of new boards (38 boards in total now) You can download it here: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r1.img.xz sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a It is important to read the README, the image standard comes without u-boot pre-loaded since u-boot is board specific. The image includes a user-friendly simple script to install the right u-boot for your board, but if you simply xzcat the image to an sdcard, and then boot your device with the sdcard, things will *not* work. See the README for a list of currently supported boards. Known Issues: -Many boards don't have an rtc (A10 and A20 have a builtin one), ?or at least no battery backup for it, resulting in the date ?+ time being wrong. -If the date is of by more then a couple of months, "yum update" ?won't work because certificate validation fails for the https ?connection yum tries to make. So if yum fails to get its repodata ?first check (and fix) your date -The regular (host not otg) usb-port on A10s based boards can be a ?bit quirky. It is best to plug in a hub even when using only one ?device, otherwise the device may not be recognized. If this happens, ?after adding a hub, often a power-cycle is needed too. -The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README ----------------------------------------------------------------- Quickstart guide ---------------- 1) Insert an sdcard, note any data on the card will be destroyed! 2) Make sure the card is not mounted, run "mount" and if the card shows ? ?up in the output umount its partitions 3) Write the img file to the card, ie as root do: ? ?xzcat Fedora-19-a10-armhfp-r1.img.xz > /dev/mmcblk0 ? ?sync 4) The card is not yet ready for use! Since the A10 u-boot is board ? ?specific, the image comes without any uboot install, follow the next ? ?steps to install the right u-boot for your board 5) Remove the card, and re-insert it. The uboot partition should get ? ?automatically mounted, if not mount it manually, 6) As root (or through sudo) run: /select-board.sh, ie: ? ?sudo /run/media/hans/uboot/select-board.sh ? ?If you've dialog installed the select-board.sh script will prompt for ? ?your board. If you don't have dialog installed, it will print the list ? ?of supported boards. Lookup your board and re-run the script with the ? ?shortname for your board as argument, ie: ? ?sudo /run/media/hans/uboot/select-board.sh mk802 7) umount the uboot and rootfs partitions, ie: ? ?umount /run/media/hans/uboot ? ?umount /run/media/hans/rootfs 8) Your sdcard is now ready for use 9) *Before* powering up your A10 device connect it to an hdmi or dvi monitor 10) When first booting from the sdcard inserted Fedora will automatically ? ?reboot once, this is part of the process to resize the root partition to ? ?fill the entire sdcard and is normal behavior. 11) After the automatic reboot Fedora will start with the initial-setup wizard: ? ?11a) Configure networking, note: ? ? ? ? * If you've an A10 board with wired ethernet and you want to use dhcp ? ? ? ? ? you don't need to do anything. ? ? ? ? * If you've an A20 board, your ethernet will have a random mac-address, ? ? ? ? ? so if you want to configure a static ip-address and want it to stick ? ? ? ? ? across reboots, go to the ethernet-tab, select the mac-address field ? ? ? ? ? and delete its contents, so that the static ip address you're ? ? ? ? ? configuring does not get tied to the random mac-address. ? ?11b) Setup the time zone ? ?11c) Set a root password ? ?11d) Create a user 12) Log in as the just created user 13) Enjoy Fedora on your A10 device Supported Devices: ------------------ Fedora 19 ARM for Allwinner A10 has been tested with the following devices: * A13-OLinuXino-MICRO (Olimex) * Auxtek T003 hdmi tv stick * Auxtek T004 hdmi tv stick * BA10 TV Box * Cubieboard development board 1024 MB RAM * Cubieboard2 (A20) development board * Gooseberry development board * Mele A1000G/A2000G 1024 MB RAM * Mini-X 1024 MB RAM * mk802 (with female mini hdmi) 512 MB RAM * mk802 with A10s (s with a circle around it on the barcode label) * mk802ii (with male normal hdmi) 1024 MB RAM * r7 hdmi tv stick * UHost U1A hdmi tv stick * Wobo i5 TV Box Fedora 19 ARM should also work on the following devices: * A10 tablet sold under various names (whitelabel) * A13 tablet sold under various names (whitelabel) * A10s-OLinuXino-MICRO (Olimex) * A13-OLinuXino (Olimex) * A20-OLinuXino-MICRO (Olimex) * Coby MID7042 tablet * Coby MID8042 tablet * Coby MID9742 tablet * Cubieboard development board 512 MB RAM * DNS AirTab M82 tablet * EOMA68 A10 CPU card * H6 netbook * Hackberry development board * Hyundai a7hd tablet * iNet-97F Rev.2 (and clones) tablet * Mele A1000/A2000 512 MB RAM * Mele A3700 * Mini-X 512 MB RAM * mk802 (with female mini hdmi) 1024 MB RAM * pcDuino development board * Point of View ProTab 2 IPS 9" tablet * Point of View ProTab 2 IPS tablet with 3g * XZPAD700 7" tablet Configuring the display output ------------------------------ Multiple video outputs at the same time are not supported. By default hdmi output with EDID is used for all devices, except for tablets/netbooks where the default output is the lcd. The default hdmi output with EDID will get the native resolution of your TV / monitor and use that. Note that in order for this to work your TV / monitor must be connected *and turned on*, before booting your device. The output resolution can be configured with the disp.screen0_output_mode kernel cmdline value, which can be found in the extrargs part of uEnv.txt in the uboot partition. The default uEnv.txt contains the following value: disp.screen0_output_mode=EDID:1280x720p60 This means try to use EDID and if no valid EDID info is found fallback to 1280x720p60. The used output can be changed by adding disp.screen0_output_type=X to the extraargs in uEnv.txt. With X being one of: 0:none; 1:lcd; 2:tv; 3:hdmi; 4:vga Some per display type notes: -lcd outputs: Hardcoded to the native mode, disp.screen0_output_mode is ignored -tv: For the cvbs output disp.screen0_output_mode must be set to one of the ?following: pal, pal-svideo, ntsc, ntsc-svideo, pal-m, pal-m-svideo, pal-nc, ?pal-nc-svideo. Note the -svideo variants should only be used on boards with ?an svideo connector, for composite out use the regular variants, ie: ?disp.screen0_output_type=2 disp.screen0_output_mode=pal -hdmi: To override the EDID detected mode, drop the "EDID:" from the ?disp.screen0_output_mode value and set it to the desired mode, ie: ?disp.screen0_output_type=3 disp.screen0_output_mode=1360x768p60 -vga: Does not support EDID, "EDID:" must be removed from the ?disp.screen0_output_mode value otherwise it will be ignored. interlaced ?progressive and refreshrate settings specified are ignored, each resolution ?has hardcoded values for these. Example usage: ?disp.screen0_output_type=4 disp.screen0_output_mode=1024x768 USB controller caveats ---------------------- The OTG USB controller in host mode only supports a limited number of devices, plugging in a hub + mouse + keyboard typically will make either the mouse or keyboard not work. This is a hardware limitation which we will likely not be able to work around. On tv-sticks and top-set boxes, simply avoid the otg connector, instead use a hub in a regular host usb connector. Note on the mini-x the otg / host marking is not always correct. If things don't work try using the OTG connector instead! On tablets and the gooseberry unfortunately only the otg connector is available. One solution there is using a single usb-device which is both a keyboard and a mouse at the same time. IE the receiver for logitech wireless desktop sets. Supported hardware components / features: ----------------------------------------- Fedora 19 ARM for Allwinner A10 supports the following components: * CPU + PMU + RAM * Serial ports * MMC cards * Internal NAND storage (*) * Framebuffer on lcd / vga / hdmi / composite video * Sound both analog out and over hdmi * OTG USB controller (*) * Both standard USB host controllers * Wifi * Wired Ethernet * SATA * IR (untested at this time) (*) *) Not supported on A20, the A20 support in the Fedora 19 A10 images is new, and as such the driver code for these has not been forward-ported from the Allwinner source dump to the sunxi-3.4 kernel the Fedora 19 A10 images use yet. Unsupported hardware components: -------------------------------- The following components require various proprietary blobs to be used, and as such are not supported in the Fedora images. The kernel drivers for them are present (usually as modules) (*), so if you add the necessary blobs you might get these to work: * Mali 400 GPU * Cedar hardware video & audio decoding and encoding engine * G2D 2d engine *) Except for the A20 Differences from stock Fedora ----------------------------- * Since the A10 is not a very powerful soc some services which are enabled by ? default on Fedora are disabled in the image, see build-image.sh for a list. * No plymouth: we log to a serial console for debugging so no pretty splash. ? Also we don't use an initrd, so removing the console=ttyS0,115200 from ? the extraargs in uEnv.txt will give plymouth, but so late it hardly matters. Rebuilding the Fedora 19 ARM for Allwinner A10 disk image --------------------------------------------------------- Building the Fedora 19 ARM for Allwinner A10 disk image consists of 2 steps 1) Building a uboot.tar.gz and rootfs.tar.gz "overlays", this is done ? ?bu the build-boot-root-sh script 2) Combining uboot.tar.gz and rootfs.tar.gz with an official Fedora 19 arm img, ? ?this combining is done by the build-image.sh script ? ?The a10 image you downloaded is based on Fedora-XFCE-armhfp-19-1-sda.raw These scripts are hosted here: https://github.com/jwrdegoede/sunxi-fedora-scripts.git A copy of the exact versions of these scripts used to build this Fedora A10 image can be found in the scripts directory of the uboot partition, the kernel config used during the build can be found here too. If you want to exactly reproduce this image it is important to use the scripts from the scripts dir of the uboot partition, as the scripts contain GIT tags used during the build to checkout the exact versions to build. The pre-conditions these scripts expect to be met, and the exact usage of them is documented in comments in the top of each script. -- devel mailing list devel at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel _______________________________________________ arm-netbook mailing list arm-netbook at lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook at files.phcomp.co.uk _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Sat Jul 20 06:57:41 2013 From: louigi600 at yahoo.it (Davide) Date: Sat, 20 Jul 2013 07:57:41 +0100 (BST) Subject: [ARMedslack] Kernel 2.10 and raspberry pi In-Reply-To: References: <20130715235859.CE5E66C598584@bmail06.one.com> Message-ID: <1374303461.67221.YahooMailNeo@web28802.mail.ir2.yahoo.com> > just been to kernel.org to see if the raspberry pi is supported. I see > no support for the device in any kernel previous to 3.10.1 which > includes support for the BCM2835. I find this odd. I would have thought > that patches would have been submitted and merged in the the kernel > tree. We still got super H Dreamcast code in there so why no Raspberry > pi? Work is still being done on 3.6.11 at raspberry pi github. Work > stopped last year on 3.2.27, so why are the patches not in kernel.org? > I don't get this. I could post this to Raspberry pi, however my feeling > is that I will not get a definitive answer. Perhaps I am > misunderstanding how the process works. Please enlighten me. Welcome to linux ARM kernel developement :-). There are patches that have never made it to main kernel on almost all the ARM hardware I've worked on (not sure if the dockstar stuff made it all to main kernel but all the zauri, the AC100 and the whole Allwinner soc family are far from that ). Regards David -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Jul 26 14:55:19 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 26 Jul 2013 15:55:19 +0100 (BST) Subject: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: <1374303015.63552.YahooMailNeo@web28802.mail.ir2.yahoo.com> References: <20130719133053.GA9965@xs4all.nl> <1374303015.63552.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: <1374850519.42950.YahooMailNeo@web28806.mail.ir2.yahoo.com> I got round to syncing my new image builder: http://ftp.slackware.org.uk/slackwarearm/people/louigi600/ Touchscreen is still not working on my device ... but if your touchscreen is on the usb bus chances are that it will work. Have fun David ________________________________ Da: Davide A: Slackware ARM port Inviato: Sabato 20 Luglio 2013 7:50 Oggetto: Re: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) My new image builder for the xzpad700 (as soon as I've time to sync it) will prepare images for all the hardware that the fedora currently supports (including the new A20 socs). as a matter of fact I\m using their bootloader and their kernels until I get round to building my own kernel.? Incidently my image builder will let you deploy any distro root filesystem tarball ... but you might need a bit of manual for non slackware root tarballs. Regards David ________________________________ Da: Ottavio Caruso A: ARMedslack at lists.armedslack.org Inviato: Venerd? 19 Luglio 2013 21:15 Oggetto: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) For whoever is interested. Maybe it's possible to port Slackware to the A20. Luke Leighton is already producing some prototypes. I've asked on the arm-netbook list if anybody is interested in seeing Slackware running on it. If that rings any bells, please give a shout. I might buy one myself if/when the device is usable. My budget is limited as I'm out ot work. ---------- Forwarded message ---------- From: "Antony Antony" Date: Jul 19, 2013 2:31 PM Subject: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) To: this is an interesting news item, though my prefeence is a debian. -antony ---------- Forwarded message ---------- Date: Thu, 18 Jul 2013 18:12:35 From: Hans de Goede To: linux-sunxi at googlegroups.com, Fedora ARM , ? ? Development discussions related to Fedora Subject: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, ? ? now with A20 support Hi All, I'm very happy to announce the first release (r1) of my Fedora 19 ARM remix images for Allwinner A10, A10s, A13 and A20 based devices. This release is based on the official Fedora 19 Final for ARM images, with u-boot and kernel(s) from the linux-sunxi project: http://linux-sunxi.org/ Besides all the goodies from Fedora-19, this release also contains the following new items on the Allwinner / sunxi front: -Support for the new dual core A20 soc (tested with cubieboard2), ?this is based on forward porting the core machine code + various ?drivers from allwinners 3.3 kernel source dump to the sunxi-3.4 ?sources. The following has been ported / is supported: ?-uarts ?-mmc controllers ?-ehci and ohci usb controllers (usb controllers 1 and 2, controller ? 0 is an otg controller and is not supported yet. ?-video output block (hdmi, vga, lcd, composite out) ?-i2c controllers ?-axp pmic including cpu voltage scaling ?-rtc ?-sound: analog in/out, hdmi audio, spdif out (spdif untested) ?-ethernet controller (emac) ?-sata controller ?Note any functional blocks in the SOC which are not explictly ?listed as supported above are not supported atm -Support for a couple of new boards (38 boards in total now) You can download it here: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r1.img.xz sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a It is important to read the README, the image standard comes without u-boot pre-loaded since u-boot is board specific. The image includes a user-friendly simple script to install the right u-boot for your board, but if you simply xzcat the image to an sdcard, and then boot your device with the sdcard, things will *not* work. See the README for a list of currently supported boards. Known Issues: -Many boards don't have an rtc (A10 and A20 have a builtin one), ?or at least no battery backup for it, resulting in the date ?+ time being wrong. -If the date is of by more then a couple of months, "yum update" ?won't work because certificate validation fails for the https ?connection yum tries to make. So if yum fails to get its repodata ?first check (and fix) your date -The regular (host not otg) usb-port on A10s based boards can be a ?bit quirky. It is best to plug in a hub even when using only one ?device, otherwise the device may not be recognized. If this happens, ?after adding a hub, often a power-cycle is needed too. -The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README ----------------------------------------------------------------- Quickstart guide ---------------- 1) Insert an sdcard, note any data on the card will be destroyed! 2) Make sure the card is not mounted, run "mount" and if the card shows ? ?up in the output umount its partitions 3) Write the img file to the card, ie as root do: ? ?xzcat Fedora-19-a10-armhfp-r1.img.xz > /dev/mmcblk0 ? ?sync 4) The card is not yet ready for use! Since the A10 u-boot is board ? ?specific, the image comes without any uboot install, follow the next ? ?steps to install the right u-boot for your board 5) Remove the card, and re-insert it. The uboot partition should get ? ?automatically mounted, if not mount it manually, 6) As root (or through sudo) run: /select-board.sh, ie: ? ?sudo /run/media/hans/uboot/select-board.sh ? ?If you've dialog installed the select-board.sh script will prompt for ? ?your board. If you don't have dialog installed, it will print the list ? ?of supported boards. Lookup your board and re-run the script with the ? ?shortname for your board as argument, ie: ? ?sudo /run/media/hans/uboot/select-board.sh mk802 7) umount the uboot and rootfs partitions, ie: ? ?umount /run/media/hans/uboot ? ?umount /run/media/hans/rootfs 8) Your sdcard is now ready for use 9) *Before* powering up your A10 device connect it to an hdmi or dvi monitor 10) When first booting from the sdcard inserted Fedora will automatically ? ?reboot once, this is part of the process to resize the root partition to ? ?fill the entire sdcard and is normal behavior. 11) After the automatic reboot Fedora will start with the initial-setup wizard: ? ?11a) Configure networking, note: ? ? ? ? * If you've an A10 board with wired ethernet and you want to use dhcp ? ? ? ? ? you don't need to do anything. ? ? ? ? * If you've an A20 board, your ethernet will have a random mac-address, ? ? ? ? ? so if you want to configure a static ip-address and want it to stick ? ? ? ? ? across reboots, go to the ethernet-tab, select the mac-address field ? ? ? ? ? and delete its contents, so that the static ip address you're ? ? ? ? ? configuring does not get tied to the random mac-address. ? ?11b) Setup the time zone ? ?11c) Set a root password ? ?11d) Create a user 12) Log in as the just created user 13) Enjoy Fedora on your A10 device Supported Devices: ------------------ Fedora 19 ARM for Allwinner A10 has been tested with the following devices: * A13-OLinuXino-MICRO (Olimex) * Auxtek T003 hdmi tv stick * Auxtek T004 hdmi tv stick * BA10 TV Box * Cubieboard development board 1024 MB RAM * Cubieboard2 (A20) development board * Gooseberry development board * Mele A1000G/A2000G 1024 MB RAM * Mini-X 1024 MB RAM * mk802 (with female mini hdmi) 512 MB RAM * mk802 with A10s (s with a circle around it on the barcode label) * mk802ii (with male normal hdmi) 1024 MB RAM * r7 hdmi tv stick * UHost U1A hdmi tv stick * Wobo i5 TV Box Fedora 19 ARM should also work on the following devices: * A10 tablet sold under various names (whitelabel) * A13 tablet sold under various names (whitelabel) * A10s-OLinuXino-MICRO (Olimex) * A13-OLinuXino (Olimex) * A20-OLinuXino-MICRO (Olimex) * Coby MID7042 tablet * Coby MID8042 tablet * Coby MID9742 tablet * Cubieboard development board 512 MB RAM * DNS AirTab M82 tablet * EOMA68 A10 CPU card * H6 netbook * Hackberry development board * Hyundai a7hd tablet * iNet-97F Rev.2 (and clones) tablet * Mele A1000/A2000 512 MB RAM * Mele A3700 * Mini-X 512 MB RAM * mk802 (with female mini hdmi) 1024 MB RAM * pcDuino development board * Point of View ProTab 2 IPS 9" tablet * Point of View ProTab 2 IPS tablet with 3g * XZPAD700 7" tablet Configuring the display output ------------------------------ Multiple video outputs at the same time are not supported. By default hdmi output with EDID is used for all devices, except for tablets/netbooks where the default output is the lcd. The default hdmi output with EDID will get the native resolution of your TV / monitor and use that. Note that in order for this to work your TV / monitor must be connected *and turned on*, before booting your device. The output resolution can be configured with the disp.screen0_output_mode kernel cmdline value, which can be found in the extrargs part of uEnv.txt in the uboot partition. The default uEnv.txt contains the following value: disp.screen0_output_mode=EDID:1280x720p60 This means try to use EDID and if no valid EDID info is found fallback to 1280x720p60. The used output can be changed by adding disp.screen0_output_type=X to the extraargs in uEnv.txt. With X being one of: 0:none; 1:lcd; 2:tv; 3:hdmi; 4:vga Some per display type notes: -lcd outputs: Hardcoded to the native mode, disp.screen0_output_mode is ignored -tv: For the cvbs output disp.screen0_output_mode must be set to one of the ?following: pal, pal-svideo, ntsc, ntsc-svideo, pal-m, pal-m-svideo, pal-nc, ?pal-nc-svideo. Note the -svideo variants should only be used on boards with ?an svideo connector, for composite out use the regular variants, ie: ?disp.screen0_output_type=2 disp.screen0_output_mode=pal -hdmi: To override the EDID detected mode, drop the "EDID:" from the ?disp.screen0_output_mode value and set it to the desired mode, ie: ?disp.screen0_output_type=3 disp.screen0_output_mode=1360x768p60 -vga: Does not support EDID, "EDID:" must be removed from the ?disp.screen0_output_mode value otherwise it will be ignored. interlaced ?progressive and refreshrate settings specified are ignored, each resolution ?has hardcoded values for these. Example usage: ?disp.screen0_output_type=4 disp.screen0_output_mode=1024x768 USB controller caveats ---------------------- The OTG USB controller in host mode only supports a limited number of devices, plugging in a hub + mouse + keyboard typically will make either the mouse or keyboard not work. This is a hardware limitation which we will likely not be able to work around. On tv-sticks and top-set boxes, simply avoid the otg connector, instead use a hub in a regular host usb connector. Note on the mini-x the otg / host marking is not always correct. If things don't work try using the OTG connector instead! On tablets and the gooseberry unfortunately only the otg connector is available. One solution there is using a single usb-device which is both a keyboard and a mouse at the same time. IE the receiver for logitech wireless desktop sets. Supported hardware components / features: ----------------------------------------- Fedora 19 ARM for Allwinner A10 supports the following components: * CPU + PMU + RAM * Serial ports * MMC cards * Internal NAND storage (*) * Framebuffer on lcd / vga / hdmi / composite video * Sound both analog out and over hdmi * OTG USB controller (*) * Both standard USB host controllers * Wifi * Wired Ethernet * SATA * IR (untested at this time) (*) *) Not supported on A20, the A20 support in the Fedora 19 A10 images is new, and as such the driver code for these has not been forward-ported from the Allwinner source dump to the sunxi-3.4 kernel the Fedora 19 A10 images use yet. Unsupported hardware components: -------------------------------- The following components require various proprietary blobs to be used, and as such are not supported in the Fedora images. The kernel drivers for them are present (usually as modules) (*), so if you add the necessary blobs you might get these to work: * Mali 400 GPU * Cedar hardware video & audio decoding and encoding engine * G2D 2d engine *) Except for the A20 Differences from stock Fedora ----------------------------- * Since the A10 is not a very powerful soc some services which are enabled by ? default on Fedora are disabled in the image, see build-image.sh for a list. * No plymouth: we log to a serial console for debugging so no pretty splash. ? Also we don't use an initrd, so removing the console=ttyS0,115200 from ? the extraargs in uEnv.txt will give plymouth, but so late it hardly matters. Rebuilding the Fedora 19 ARM for Allwinner A10 disk image --------------------------------------------------------- Building the Fedora 19 ARM for Allwinner A10 disk image consists of 2 steps 1) Building a uboot.tar.gz and rootfs.tar.gz "overlays", this is done ? ?bu the build-boot-root-sh script 2) Combining uboot.tar.gz and rootfs.tar.gz with an official Fedora 19 arm img, ? ?this combining is done by the build-image.sh script ? ?The a10 image you downloaded is based on Fedora-XFCE-armhfp-19-1-sda.raw These scripts are hosted here: https://github.com/jwrdegoede/sunxi-fedora-scripts.git A copy of the exact versions of these scripts used to build this Fedora A10 image can be found in the scripts directory of the uboot partition, the kernel config used during the build can be found here too. If you want to exactly reproduce this image it is important to use the scripts from the scripts dir of the uboot partition, as the scripts contain GIT tags used during the build to checkout the exact versions to build. The pre-conditions these scripts expect to be met, and the exact usage of them is documented in comments in the top of each script. -- devel mailing list devel at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel _______________________________________________ arm-netbook mailing list arm-netbook at lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook at files.phcomp.co.uk _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Fri Jul 26 14:55:19 2013 From: louigi600 at yahoo.it (Davide) Date: Fri, 26 Jul 2013 15:55:19 +0100 (BST) Subject: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: <1374303015.63552.YahooMailNeo@web28802.mail.ir2.yahoo.com> References: <20130719133053.GA9965@xs4all.nl> <1374303015.63552.YahooMailNeo@web28802.mail.ir2.yahoo.com> Message-ID: <1374850519.42950.YahooMailNeo@web28806.mail.ir2.yahoo.com> I got round to syncing my new image builder: http://ftp.slackware.org.uk/slackwarearm/people/louigi600/ Touchscreen is still not working on my device ... but if your touchscreen is on the usb bus chances are that it will work. Have fun David ________________________________ Da: Davide A: Slackware ARM port Inviato: Sabato 20 Luglio 2013 7:50 Oggetto: Re: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) My new image builder for the xzpad700 (as soon as I've time to sync it) will prepare images for all the hardware that the fedora currently supports (including the new A20 socs). as a matter of fact I\m using their bootloader and their kernels until I get round to building my own kernel.? Incidently my image builder will let you deploy any distro root filesystem tarball ... but you might need a bit of manual for non slackware root tarballs. Regards David ________________________________ Da: Ottavio Caruso A: ARMedslack at lists.armedslack.org Inviato: Venerd? 19 Luglio 2013 21:15 Oggetto: [ARMedslack] Fwd: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) For whoever is interested. Maybe it's possible to port Slackware to the A20. Luke Leighton is already producing some prototypes. I've asked on the arm-netbook list if anybody is interested in seeing Slackware running on it. If that rings any bells, please give a shout. I might buy one myself if/when the device is usable. My budget is limited as I'm out ot work. ---------- Forwarded message ---------- From: "Antony Antony" Date: Jul 19, 2013 2:31 PM Subject: Re: [Arm-netbook] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) To: this is an interesting news item, though my prefeence is a debian. -antony ---------- Forwarded message ---------- Date: Thu, 18 Jul 2013 18:12:35 From: Hans de Goede To: linux-sunxi at googlegroups.com, Fedora ARM , ? ? Development discussions related to Fedora Subject: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, ? ? now with A20 support Hi All, I'm very happy to announce the first release (r1) of my Fedora 19 ARM remix images for Allwinner A10, A10s, A13 and A20 based devices. This release is based on the official Fedora 19 Final for ARM images, with u-boot and kernel(s) from the linux-sunxi project: http://linux-sunxi.org/ Besides all the goodies from Fedora-19, this release also contains the following new items on the Allwinner / sunxi front: -Support for the new dual core A20 soc (tested with cubieboard2), ?this is based on forward porting the core machine code + various ?drivers from allwinners 3.3 kernel source dump to the sunxi-3.4 ?sources. The following has been ported / is supported: ?-uarts ?-mmc controllers ?-ehci and ohci usb controllers (usb controllers 1 and 2, controller ? 0 is an otg controller and is not supported yet. ?-video output block (hdmi, vga, lcd, composite out) ?-i2c controllers ?-axp pmic including cpu voltage scaling ?-rtc ?-sound: analog in/out, hdmi audio, spdif out (spdif untested) ?-ethernet controller (emac) ?-sata controller ?Note any functional blocks in the SOC which are not explictly ?listed as supported above are not supported atm -Support for a couple of new boards (38 boards in total now) You can download it here: http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r1.img.xz sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a It is important to read the README, the image standard comes without u-boot pre-loaded since u-boot is board specific. The image includes a user-friendly simple script to install the right u-boot for your board, but if you simply xzcat the image to an sdcard, and then boot your device with the sdcard, things will *not* work. See the README for a list of currently supported boards. Known Issues: -Many boards don't have an rtc (A10 and A20 have a builtin one), ?or at least no battery backup for it, resulting in the date ?+ time being wrong. -If the date is of by more then a couple of months, "yum update" ?won't work because certificate validation fails for the https ?connection yum tries to make. So if yum fails to get its repodata ?first check (and fix) your date -The regular (host not otg) usb-port on A10s based boards can be a ?bit quirky. It is best to plug in a hub even when using only one ?device, otherwise the device may not be recognized. If this happens, ?after adding a hub, often a power-cycle is needed too. -The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm Enjoy, Hans And to make sure everyone reads the README, let me print it here in full: Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README ----------------------------------------------------------------- Quickstart guide ---------------- 1) Insert an sdcard, note any data on the card will be destroyed! 2) Make sure the card is not mounted, run "mount" and if the card shows ? ?up in the output umount its partitions 3) Write the img file to the card, ie as root do: ? ?xzcat Fedora-19-a10-armhfp-r1.img.xz > /dev/mmcblk0 ? ?sync 4) The card is not yet ready for use! Since the A10 u-boot is board ? ?specific, the image comes without any uboot install, follow the next ? ?steps to install the right u-boot for your board 5) Remove the card, and re-insert it. The uboot partition should get ? ?automatically mounted, if not mount it manually, 6) As root (or through sudo) run: /select-board.sh, ie: ? ?sudo /run/media/hans/uboot/select-board.sh ? ?If you've dialog installed the select-board.sh script will prompt for ? ?your board. If you don't have dialog installed, it will print the list ? ?of supported boards. Lookup your board and re-run the script with the ? ?shortname for your board as argument, ie: ? ?sudo /run/media/hans/uboot/select-board.sh mk802 7) umount the uboot and rootfs partitions, ie: ? ?umount /run/media/hans/uboot ? ?umount /run/media/hans/rootfs 8) Your sdcard is now ready for use 9) *Before* powering up your A10 device connect it to an hdmi or dvi monitor 10) When first booting from the sdcard inserted Fedora will automatically ? ?reboot once, this is part of the process to resize the root partition to ? ?fill the entire sdcard and is normal behavior. 11) After the automatic reboot Fedora will start with the initial-setup wizard: ? ?11a) Configure networking, note: ? ? ? ? * If you've an A10 board with wired ethernet and you want to use dhcp ? ? ? ? ? you don't need to do anything. ? ? ? ? * If you've an A20 board, your ethernet will have a random mac-address, ? ? ? ? ? so if you want to configure a static ip-address and want it to stick ? ? ? ? ? across reboots, go to the ethernet-tab, select the mac-address field ? ? ? ? ? and delete its contents, so that the static ip address you're ? ? ? ? ? configuring does not get tied to the random mac-address. ? ?11b) Setup the time zone ? ?11c) Set a root password ? ?11d) Create a user 12) Log in as the just created user 13) Enjoy Fedora on your A10 device Supported Devices: ------------------ Fedora 19 ARM for Allwinner A10 has been tested with the following devices: * A13-OLinuXino-MICRO (Olimex) * Auxtek T003 hdmi tv stick * Auxtek T004 hdmi tv stick * BA10 TV Box * Cubieboard development board 1024 MB RAM * Cubieboard2 (A20) development board * Gooseberry development board * Mele A1000G/A2000G 1024 MB RAM * Mini-X 1024 MB RAM * mk802 (with female mini hdmi) 512 MB RAM * mk802 with A10s (s with a circle around it on the barcode label) * mk802ii (with male normal hdmi) 1024 MB RAM * r7 hdmi tv stick * UHost U1A hdmi tv stick * Wobo i5 TV Box Fedora 19 ARM should also work on the following devices: * A10 tablet sold under various names (whitelabel) * A13 tablet sold under various names (whitelabel) * A10s-OLinuXino-MICRO (Olimex) * A13-OLinuXino (Olimex) * A20-OLinuXino-MICRO (Olimex) * Coby MID7042 tablet * Coby MID8042 tablet * Coby MID9742 tablet * Cubieboard development board 512 MB RAM * DNS AirTab M82 tablet * EOMA68 A10 CPU card * H6 netbook * Hackberry development board * Hyundai a7hd tablet * iNet-97F Rev.2 (and clones) tablet * Mele A1000/A2000 512 MB RAM * Mele A3700 * Mini-X 512 MB RAM * mk802 (with female mini hdmi) 1024 MB RAM * pcDuino development board * Point of View ProTab 2 IPS 9" tablet * Point of View ProTab 2 IPS tablet with 3g * XZPAD700 7" tablet Configuring the display output ------------------------------ Multiple video outputs at the same time are not supported. By default hdmi output with EDID is used for all devices, except for tablets/netbooks where the default output is the lcd. The default hdmi output with EDID will get the native resolution of your TV / monitor and use that. Note that in order for this to work your TV / monitor must be connected *and turned on*, before booting your device. The output resolution can be configured with the disp.screen0_output_mode kernel cmdline value, which can be found in the extrargs part of uEnv.txt in the uboot partition. The default uEnv.txt contains the following value: disp.screen0_output_mode=EDID:1280x720p60 This means try to use EDID and if no valid EDID info is found fallback to 1280x720p60. The used output can be changed by adding disp.screen0_output_type=X to the extraargs in uEnv.txt. With X being one of: 0:none; 1:lcd; 2:tv; 3:hdmi; 4:vga Some per display type notes: -lcd outputs: Hardcoded to the native mode, disp.screen0_output_mode is ignored -tv: For the cvbs output disp.screen0_output_mode must be set to one of the ?following: pal, pal-svideo, ntsc, ntsc-svideo, pal-m, pal-m-svideo, pal-nc, ?pal-nc-svideo. Note the -svideo variants should only be used on boards with ?an svideo connector, for composite out use the regular variants, ie: ?disp.screen0_output_type=2 disp.screen0_output_mode=pal -hdmi: To override the EDID detected mode, drop the "EDID:" from the ?disp.screen0_output_mode value and set it to the desired mode, ie: ?disp.screen0_output_type=3 disp.screen0_output_mode=1360x768p60 -vga: Does not support EDID, "EDID:" must be removed from the ?disp.screen0_output_mode value otherwise it will be ignored. interlaced ?progressive and refreshrate settings specified are ignored, each resolution ?has hardcoded values for these. Example usage: ?disp.screen0_output_type=4 disp.screen0_output_mode=1024x768 USB controller caveats ---------------------- The OTG USB controller in host mode only supports a limited number of devices, plugging in a hub + mouse + keyboard typically will make either the mouse or keyboard not work. This is a hardware limitation which we will likely not be able to work around. On tv-sticks and top-set boxes, simply avoid the otg connector, instead use a hub in a regular host usb connector. Note on the mini-x the otg / host marking is not always correct. If things don't work try using the OTG connector instead! On tablets and the gooseberry unfortunately only the otg connector is available. One solution there is using a single usb-device which is both a keyboard and a mouse at the same time. IE the receiver for logitech wireless desktop sets. Supported hardware components / features: ----------------------------------------- Fedora 19 ARM for Allwinner A10 supports the following components: * CPU + PMU + RAM * Serial ports * MMC cards * Internal NAND storage (*) * Framebuffer on lcd / vga / hdmi / composite video * Sound both analog out and over hdmi * OTG USB controller (*) * Both standard USB host controllers * Wifi * Wired Ethernet * SATA * IR (untested at this time) (*) *) Not supported on A20, the A20 support in the Fedora 19 A10 images is new, and as such the driver code for these has not been forward-ported from the Allwinner source dump to the sunxi-3.4 kernel the Fedora 19 A10 images use yet. Unsupported hardware components: -------------------------------- The following components require various proprietary blobs to be used, and as such are not supported in the Fedora images. The kernel drivers for them are present (usually as modules) (*), so if you add the necessary blobs you might get these to work: * Mali 400 GPU * Cedar hardware video & audio decoding and encoding engine * G2D 2d engine *) Except for the A20 Differences from stock Fedora ----------------------------- * Since the A10 is not a very powerful soc some services which are enabled by ? default on Fedora are disabled in the image, see build-image.sh for a list. * No plymouth: we log to a serial console for debugging so no pretty splash. ? Also we don't use an initrd, so removing the console=ttyS0,115200 from ? the extraargs in uEnv.txt will give plymouth, but so late it hardly matters. Rebuilding the Fedora 19 ARM for Allwinner A10 disk image --------------------------------------------------------- Building the Fedora 19 ARM for Allwinner A10 disk image consists of 2 steps 1) Building a uboot.tar.gz and rootfs.tar.gz "overlays", this is done ? ?bu the build-boot-root-sh script 2) Combining uboot.tar.gz and rootfs.tar.gz with an official Fedora 19 arm img, ? ?this combining is done by the build-image.sh script ? ?The a10 image you downloaded is based on Fedora-XFCE-armhfp-19-1-sda.raw These scripts are hosted here: https://github.com/jwrdegoede/sunxi-fedora-scripts.git A copy of the exact versions of these scripts used to build this Fedora A10 image can be found in the scripts directory of the uboot partition, the kernel config used during the build can be found here too. If you want to exactly reproduce this image it is important to use the scripts from the scripts dir of the uboot partition, as the scripts contain GIT tags used during the build to checkout the exact versions to build. The pre-conditions these scripts expect to be met, and the exact usage of them is documented in comments in the top of each script. -- devel mailing list devel at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel _______________________________________________ arm-netbook mailing list arm-netbook at lists.phcomp.co.uk http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook Send large attachments to arm-netbook at files.phcomp.co.uk _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From ottavio2006-usenet2012 at yahoo.com Fri Jul 26 21:29:42 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Fri, 26 Jul 2013 22:29:42 +0100 Subject: [ARMedslack] Generic Allwinner Slackware installer, was: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) Message-ID: On 26 July 2013 15:55, Davide wrote: > I got round to syncing my new image builder: > http://ftp.slackware.org.uk/slackwarearm/people/louigi600/ > > > Touchscreen is still not working on my device ... but if your touchscreen is > on the usb bus chances are that it will work. > > Have fun > David Thanks Davide. I haven't got a a20 (or earlier) device to play with (yet), but I am forwarding this email to arm-netbook. I hope this will raise interest of having Slackware on the Allwinner. -- Ottavio From m-lists at biscuit.org.uk Fri Jul 26 21:35:40 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Fri, 26 Jul 2013 22:35:40 +0100 (BST) Subject: [ARMedslack] Generic Allwinner Slackware installer, was: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: References: Message-ID: > I haven't got a a20 (or earlier) device to play with (yet), but I am > forwarding this email to arm-netbook. I hope this will raise interest > of having Slackware on the Allwinner. I am preparing a generic armv6 and onwards Linux 3.10 kernel (the separate 'kirkwood' and 'versatile' kernels will remain as is because the armv5 support has not been consolidated). Initially I'll make sure that the existing 'Tegra' works since that's what I'm using as the main build machine, but I have also added support for Allwinner: [*] Allwinner A1X SOCs Of course, there will be plenty of other drivers and so on that would be required which someone can furnish me with at a later date once I push out the kernels. From louigi600 at yahoo.it Sat Jul 27 18:26:41 2013 From: louigi600 at yahoo.it (Davide) Date: Sat, 27 Jul 2013 19:26:41 +0100 (BST) Subject: [ARMedslack] Generic Allwinner Slackware installer, was: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: References: Message-ID: <1374949601.71855.YahooMailNeo@web28803.mail.ir2.yahoo.com> >> I haven't got a a20 (or earlier) device to play with (yet), but I am >> forwarding this email to arm-netbook. I hope this will raise interest >> of having Slackware on the Allwinner. >I am preparing a generic armv6 and onwards Linux 3.10 kernel (the >separate 'kirkwood' and 'versatile' kernels will remain as is because the >armv5 support has not been consolidated). >Initially I'll make sure that the existing 'Tegra' works since that's what I'm using >as the main build machine, but I have also added support for Allwinner: >[*] Allwinner A1X SOCs >Of course, there will be plenty of other drivers and so on that would be >required which someone can furnish me with at a later date once I push out >the kernels. Supporting Allwinner SOC would really probabbly require a 3.0 or a 3.4 kernel from the linux-sunxi branch (https://github.com/linux-sunxi/linux-sunxi) as many patches have not made it to kernel.org, or searching around for the patches to apply to vanilla kernel (that will will be probabbly conceived for ither a 3.0 or a 3.4 kernel anyway). But if you come up with something to test I can see if it works on my XZPAD700. ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanley at stanleygarvey.com Sat Jul 27 21:33:28 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sat, 27 Jul 2013 22:33:28 +0100 Subject: [ARMedslack] Generic Allwinner Slackware installer, was: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: <1374949601.71855.YahooMailNeo@web28803.mail.ir2.yahoo.com> References: <1374949601.71855.YahooMailNeo@web28803.mail.ir2.yahoo.com> Message-ID: <20130727213328.94418F32CD11F@bmail-n01.one.com> On Jul 27, 2013 19:26 "Davide" wrote: > > > >> I haven't got a a20 (or earlier) device to play with (yet), but I > >> am > >> forwarding this email to arm-netbook. I hope this will raise > >> interest > >> of having Slackware on the Allwinner. > > >I am preparing a generic armv6 and onwards Linux 3.10 kernel (the > >separate 'kirkwood' and 'versatile' kernels will remain as is because > >the > >armv5 support has not been consolidated). > > >Initially I'll make sure that the existing 'Tegra' works since that's > >what I'm using > >as the main build machine, but I have also added support for > >Allwinner: > > >[*] Allwinner A1X SOCs > > >Of course, there will be plenty of other drivers and so on that would > >be > >required which someone can furnish me with at a later date once I > >push out > >the kernels. > > Supporting Allwinner SOC would really probabbly require a 3.0 or a 3.4 > kernel from the linux-sunxi branch > (https://github.com/linux-sunxi/linux-sunxi) as many patches have not > made it to kernel.org, or searching around for the patches to apply to > vanilla kernel (that will will be probabbly conceived for ither a 3.0 > or a 3.4 kernel anyway). > But if you come up with something to test I can see if it works on my > XZPAD700. > > ATB > David > > I noticed RPi patches also not making it into kernel.org. Last weekend > I tried to compile a generic 3.10.1 kernel for the RPi and it failed > to boot. Rather than patch kernel source for a specific ARM target, > are we expected to use the generic kernel and build a device tree > binary? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Sun Jul 28 08:52:03 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Sun, 28 Jul 2013 09:52:03 +0100 (BST) Subject: [ARMedslack] Generic Allwinner Slackware installer, was: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: <20130727213328.94418F32CD11F@bmail-n01.one.com> References: <1374949601.71855.YahooMailNeo@web28803.mail.ir2.yahoo.com> <20130727213328.94418F32CD11F@bmail-n01.one.com> Message-ID: > > I noticed RPi patches also not making it into kernel.org. Last weekend > > I tried to compile a generic 3.10.1 kernel for the RPi and it failed > > to boot. Rather than patch kernel source for a specific ARM target, > > are we expected to use the generic kernel and build a device tree > > binary? That's the idea, yes except that you wouldn't have to build the device tree blob since if support is compiled into the kernel for that device, then the DTB would already have been built and would be provided with the kernel package. The DTBs are generated by kernel.SlackBuild for the specific architectures, so once additional support is added, the architecture name will need to be appended to the list for the specific kernel. I tried to build an armv6 and armv7 generic kernel, but since the base line is set to armv6, when armv7 code begins to build, it fails since the ARMv6 CPUs cannot execute v7 instructions. I don't understand why you can select both CPUs in this case. You need to select ARMv7 to choose the hardware that has a v7 CPU. I guess the whole thing isn't entirely complete yet, or perhaps I'm misunderstanding what you can do with it. Needless to say, I'm building a ganeric armv7 kernel now. -- Stuart Winter Slackware ARM: http://arm.slackware.com From stanley at stanleygarvey.com Sun Jul 28 09:19:19 2013 From: stanley at stanleygarvey.com (stanley garvey) Date: Sun, 28 Jul 2013 10:19:19 +0100 Subject: [ARMedslack] Generic Allwinner Slackware installer, was: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: References: <20130727213328.94418F32CD11F@bmail-n01.one.com> Message-ID: <20130728091919.A73349FAC7A05@bmail04.one.com> On Jul 28, 2013 09:52 "Stuart Winter" wrote: > > > I noticed RPi patches also not making it into kernel.org. Last > > > weekend > > > I tried to compile a generic 3.10.1 kernel for the RPi and it > > > failed > > > to boot. Rather than patch kernel source for a specific ARM > > > target, > > > are we expected to use the generic kernel and build a device tree > > > binary? > > That's the idea, yes except that you wouldn't have to build the device > tree blob since if support is compiled into the kernel for that > device, > then the DTB would already have been built and would be provided with > the > kernel package. The DTBs are generated by kernel.SlackBuild for the > specific architectures, so once additional support is added, the > architecture name will need to be appended to the list for the > specific > kernel. > > I tried to build an armv6 and armv7 generic kernel, but since the base > line is set to armv6, when armv7 code begins to build, it fails since > the > ARMv6 CPUs cannot execute v7 instructions. I don't understand why you > can > select both CPUs in this case. You need to select ARMv7 to choose the > hardware that has a v7 CPU. I guess the whole thing isn't entirely > complete yet, or perhaps I'm misunderstanding what you can do with it. > Needless to say, I'm building a ganeric armv7 kernel now. > > Thanks for that, I am building a generic armv6 kernel now, using the > bcm2835_defconfig. hoping it will boot later today. This is what I > should have done in the first place rather than trying to make > oldconfig :( then I can make any tweeks it may require. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Sun Jul 28 16:01:15 2013 From: louigi600 at yahoo.it (Davide) Date: Sun, 28 Jul 2013 17:01:15 +0100 (BST) Subject: [ARMedslack] Generic Allwinner Slackware installer, was: Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support (fwd) In-Reply-To: References: <1374949601.71855.YahooMailNeo@web28803.mail.ir2.yahoo.com> <20130727213328.94418F32CD11F@bmail-n01.one.com> Message-ID: <1375027275.37919.YahooMailNeo@web28806.mail.ir2.yahoo.com> >> > I noticed RPi patches also not making it into kernel.org. Last weekend >> > I tried to compile a generic 3.10.1 kernel for the RPi and it failed >> > to boot. Rather than patch kernel source for a specific ARM target, >> > are we expected to use the generic kernel and build a device tree >> > binary? >That's the idea, yes except that you wouldn't have to build the device >tree blob since if support is compiled into the kernel for that device, >then the DTB would already have been built and? be provided with the >kernel package.? The DTBs are generated by kernel.SlackBuild for the >specific architectures, so once additional support is added, the >architecture name will need to be appended to the list for the specific >kernel. >I tried to build an armv6 and armv7 generic kernel, but since the base >line is set to armv6, when armv7 code begins to build, it fails since the >ARMv6 CPUs cannot execute v7 instructions.? I don't understand why you can >select both CPUs in this case.? You need to select ARMv7 to choose the >hardware that has a v7 CPU.? I guess the whole thing isn't entirely >complete yet, or perhaps I'm misunderstanding what you can do with it. >Needless to say, I'm building a ganeric armv7 kernel now. Not sure if what comes with fedora is built for armv7 or notbut they do have 3 kernels respectively for sin5i sun5i and sun7i. I'll checkout as soon as I get to use my XZPAD700 again and I'll have an answer for the sun5i core. ATB David -------------- next part -------------- An HTML attachment was scrubbed... URL: From nsollars at gmail.com Sun Jul 28 19:55:54 2013 From: nsollars at gmail.com (Nigel Sollars) Date: Sun, 28 Jul 2013 15:55:54 -0400 Subject: [ARMedslack] Current status of arm ports eabihf Message-ID: Hi, Ive been away for a while, just thought id ask what the current state of a 32bit hf port is. Id like to test anything available on my Panda. One question I have is, is the Linaro toolchain used in the slackport?. Nige -- ?Science is a differential equation. Religion is a boundary condition.? Alan Turing -------------- next part -------------- An HTML attachment was scrubbed... URL: From ottavio2006-usenet2012 at yahoo.com Sun Jul 28 20:17:45 2013 From: ottavio2006-usenet2012 at yahoo.com (Ottavio Caruso) Date: Sun, 28 Jul 2013 21:17:45 +0100 Subject: [ARMedslack] Current status of arm ports eabihf In-Reply-To: References: Message-ID: On Jul 28, 2013 8:56 PM, "Nigel Sollars" wrote: > > Hi, > > Ive been away for a while, just thought id ask what the current state of a 32bit hf port is. > I think the hf port is Eric's pet project but I could be wrong. > One question I have is, is the Linaro toolchain used in the slackport?. I'd like to see that but I suspect it needs cross compiling on a Ubuntu host. Not that it wouldn't be technical possible to cross compile on a Slackware host or any host, but... > Nige > > -- > ?Science is a differential equation. Religion is a boundary condition.? > Alan Turing > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nsollars at gmail.com Sun Jul 28 20:33:12 2013 From: nsollars at gmail.com (Nigel Sollars) Date: Sun, 28 Jul 2013 16:33:12 -0400 Subject: [ARMedslack] Current status of arm ports eabihf In-Reply-To: References: Message-ID: On Sun, Jul 28, 2013 at 4:17 PM, Ottavio Caruso < ottavio2006-usenet2012 at yahoo.com> wrote: > > On Jul 28, 2013 8:56 PM, "Nigel Sollars" wrote: > > > > Hi, > > > > Ive been away for a while, just thought id ask what the current state > of a 32bit hf port is. > > > > I think the hf port is Eric's pet project but I could be wrong. > I was looking at the blog actually, seems like the right direction. Be cool to see how the trimslice is working out. > One question I have is, is the Linaro toolchain used in the slackport?. > > I'd like to see that but I suspect it needs cross compiling on a Ubuntu > host. Not that it wouldn't be technical possible to cross compile on a > Slackware host or any host, but... > > You could be right, Here is what I was hoping, is that a very simple ( mini ) root would be available ( and I mean mini ) with a working native compiler. I want to test the latter 3.10 released kernels as the Arm branch is very active with some nice fixes. For Embedded the most important is core support for better GPIO control. Ive gotten all the hardware working on the Panda, Wifi BT etc etc etc. But most probably not overly optimal. Nige > > Nige > > > > -- > > ?Science is a differential equation. Religion is a boundary condition.? > > > Alan Turing > > > > _______________________________________________ > > ARMedslack mailing list > > ARMedslack at lists.armedslack.org > > http://lists.armedslack.org/mailman/listinfo/armedslack > > > > > _______________________________________________ > ARMedslack mailing list > ARMedslack at lists.armedslack.org > http://lists.armedslack.org/mailman/listinfo/armedslack > > -- ?Science is a differential equation. Religion is a boundary condition.? Alan Turing -------------- next part -------------- An HTML attachment was scrubbed... URL: From louigi600 at yahoo.it Mon Jul 29 14:37:43 2013 From: louigi600 at yahoo.it (Davide) Date: Mon, 29 Jul 2013 15:37:43 +0100 (BST) Subject: [ARMedslack] Current status of arm ports eabihf In-Reply-To: References: Message-ID: <1375108663.89342.YahooMailNeo@web28806.mail.ir2.yahoo.com> Sorry mixing html and standard ">" indentation on yahoo means a lot of manual editing. Taking the ordinary slackware miniroot to one with compiler is really just a matter of installing some packages (in the d and l series ). I often do that on a live system just after having gotten networking and slackpkg working. If you look at the build script you can add what ever packages you need and build your own custom miniroot. But be aware that slackpkg (and possibly some other packages) will setup things on the host detected architecture so even if you install packages to e different? root some configuration is done wrong , like for example slackpkg only having the x86 mirrors in the mirror list. Nothing you can't put right by hand but something you mignht want to know befor you start off. ATB David ________________________________ Da: Nigel Sollars A: Slackware ARM port Inviato: Domenica 28 Luglio 2013 21:33 Oggetto: Re: [ARMedslack] Current status of arm ports eabihf On Sun, Jul 28, 2013 at 4:17 PM, Ottavio Caruso wrote: >On Jul 28, 2013 8:56 PM, "Nigel Sollars" wrote: >> >> Hi, >> >> Ive been away for a while, ?just thought id ask what the current state of a 32bit hf port is. >> > >I think the hf port is Eric's pet project but I could be wrong. > I was looking at the blog actually, ?seems like the right direction. ?Be cool to see how the trimslice is working out. > One question I have is, is the Linaro toolchain used in the slackport?. > >I'd like to see that but I suspect it needs cross compiling on a Ubuntu host. Not that it wouldn't be technical possible to cross compile on a Slackware host or any host, but... > > You could be right, Here is what I was hoping, is that a very simple ( mini ) root would be available ( and I mean mini ) with a working native compiler. ?I want to test the latter 3.10 released kernels as the Arm branch is very active with some nice fixes. ?For Embedded the most important is core support for better GPIO control. Ive gotten all the hardware working on the Panda, ?Wifi BT etc etc etc. ?But most probably not overly optimal. Nige > ?Nige >> >> -- >> ?Science is a differential equation. Religion is a boundary condition.? >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Alan Turing >> > > _______________________________________________ >> ARMedslack mailing list >> ARMedslack at lists.armedslack.org >> http://lists.armedslack.org/mailman/listinfo/armedslack >> > >_______________________________________________ >ARMedslack mailing list >ARMedslack at lists.armedslack.org >http://lists.armedslack.org/mailman/listinfo/armedslack > > -- ?Science is a differential equation. Religion is a boundary condition.? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Alan Turing _______________________________________________ ARMedslack mailing list ARMedslack at lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -------------- next part -------------- An HTML attachment was scrubbed... URL: From m-lists at biscuit.org.uk Mon Jul 29 14:51:05 2013 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Mon, 29 Jul 2013 15:51:05 +0100 (BST) Subject: [ARMedslack] Current status of arm ports eabihf In-Reply-To: References: Message-ID: > One question I have is, is the Linaro toolchain used in the slackport?. The patches are in the diff that's applied, but the linaro ones are not applied at build time. I did at one point try adding the linaro patches, but some hunks indicated that they were already applied -- so I left it. It probably wouldn't be too much work to add the linaro patches in from the diff that's in the source tree, and rebuild the gcc package. -- Stuart Winter Slackware ARM: http://arm.slackware.com