Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can't say I'm a fan of the forum format, IMHO and experience it just gives people the chance to get nasty and personal, but I guess this is where it's going to be now.
Congratulation for the new (sub-)forum, dedicated entirely for the Slackware on the nobble ARM platform!
And, I have a (maybe a stupid) question.
This sub-forum is dedicated entirely for the Official Slackware ARM, aka Dr. Mozes's Slackware ARM, or there is room also for another Slackware(-based) ARM ports, i.e. the AlienBOB's Slackware ARM or whatever Slackware ARM port/build?
Last edited by Darth Vader; 12-05-2013 at 04:10 AM.
This sub-forum is dedicated entirely for the Official Slackware ARM, aka Dr. Mozes's Slackware ARM, or there is room also for another Slackware(-based) ARM ports, i.e. the AlienBOB's Slackware ARM or whatever Slackware ARM port/build?
That's a very good question: here are my thoughts
Since Slackware does not have a hardware floating point ARM port, when AlienBOB's port is progressing and released, I don't see any reason why it also could not be an official port if he wanted it to be - so it'd be good to have threads related to his work in here as well, unless he wants them to be elsewhere.
Regarding other derivative works - I'd be less willing to 'cross polinate' the efforts: solely because people already don't read documentation (not that this is anything new - I've made good money through that in other areas of life ;-) ) and tarnish the Slackware brand with FUD and total nonsense. Given that derived works (or independent Slackware-based works) are not 'Slackware' (approved by Patrick), I don't feel that they belong in the 'Slackware ARM' forum and would prefer them to be elsewhere.
Thank you for quick response, and now I have a question about what you call derivative works under (Slackware) ARM.
Like you know, the ARM platforms requires a special treatment. Most of devices, even they are very common, i.e. consumer devices, like netbooks or mini-pcs, require special compiled kernels, with special patches, even special toolchains (to build the kernel) and special user-land support, including tools and configuration. For example, from what I known, one of the most complete (but non-standard) ports of Slackware ARM, including even the accelerated graphics, can be done under the Rockchip RK3066/3188 devices.
Still, even the operating system, sine-die, is right the Slackware ARM, the named Rockchip RK3066 port will present specific quirks and problems, even specific packages.
The question is, there is room also, for the threads and problems strictly specific of a ... lets call it ... "community supported" device?
But, that page talks about that there are acceptable just the modified packages (also the specific minirootfs and kernels), for the named port to be considered a "community supported device"...
Still, yet, for a successful port to an RK3066 device, for example, to have a complete experience, require integration of some new packages, for MALI graphics support, etc. I.e. xfree86-video-mali, or even better, xfree86-video-rk30fb, also, maybe, of even the proprietary MALI's OpenGLES libraries.
The question is, even after the inclusion of a relative small number of device specific packages, that Slackware ARM port is qualified as "community supported device"?
Last edited by Darth Vader; 12-06-2013 at 04:48 AM.
But, that page talks about that there are acceptable just the modified packages (also the specific minirootfs and kernels), for the named port to be considered a "community supported device"...
I don't consider adding some packages or kernels a 'port' as it doesn't fit into the meaning of that definition. For example, I don't say I've now 'ported' Slackware to the ARM Versatile platform - I just added 'support'.
Quote:
Originally Posted by Darth Vader
packages, for MALI graphics support, etc. I.e. xfree86-video-mali, or even better, xfree86-video-rk30fb, also, maybe, of even the proprietary MALI's OpenGLES libraries.
The OpenGLES libraries are included in Mesa though aren't they? They would not be proprietary though.
If you were including proprietary libraries, you'd need to ensure that you obtained the agreement with the owner of them to ship them, and you should also include an adjustment/new copyright notice - see 'COPYRIGHT.TXT' in the root dir.
Quote:
Originally Posted by Darth Vader
The question is, even after the inclusion of a relative small number of device specific packages, that Slackware ARM port is qualified as "community supported device"?
Ah yes - that's a good point: I have updated the page.
I'm new on LinuxQuestions but using Slackware for at least 17 years, the last two also on ARM.
I wasn't aware about this forum until I got a google result pointing at it and I became so happy to find out that there are others Slack addicted like-minded out here. Happy to meet you!
I started a new thread on Slackware ARM yesterday, related to the Raspberry kernel on Slack ARM and today I edited to correct two spelling mistakes and to add some technical details. After updating it, I got logged out by LinuxQuestion, had displayed an apology and a hint = I should contact the administrators, which I did. Meanwhile, the thread disappeared and trying to put it back I constantly get, your post needs moderators approval.
I hope that my thread will finally appear back on one sunny day.
I'm new on LinuxQuestions but using Slackware for at least 17 years, the last two also on ARM.
I wasn't aware about this forum until I got a google result pointing at it and I became so happy to find out that there are others Slack addicted like-minded out here. Happy to meet you!
I started a new thread on Slackware ARM yesterday, related to the Raspberry kernel on Slack ARM and today I edited to correct two spelling mistakes and to add some technical details. After updating it, I got logged out by LinuxQuestion, had displayed an apology and a hint = I should contact the administrators, which I did. Meanwhile, the thread disappeared and trying to put it back I constantly get, your post needs moderators approval.
I hope that my thread will finally appear back on one sunny day.
Again, happy to meet you!
Hello
I saw your thread and assumed you'd deleted it. I don't know why it was removed.
Perhaps re-post it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.