[ARMedslack] armedslack on android phone?

[stanley garvey]

On Jul 14, 2013 10:22 "Davide" <louigi600 at yahoo.it> 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 <gorecki at fastguys.net>
> A: 'Slackware ARM port' <armedslack at lists.armedslack.org>
> 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 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
> <ARMedslack at lists.armedslack.org>
> <http://lists.armedslack.org/mailman/listinfo/armedslack>
> 
> 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: <http://lists.armedslack.org/pipermail/armedslack/attachments/20130714/b0155ea4/attachment.html>