Hi,
It seem that many people are trying to compile kernel from different source
but are unable to compile a good kernel ( i do it myself ). It will be easier if olimex can provide source and config used to have a good base using the r2 image.
This will let people effort concentrate in the same direction.
I know that this is summer holiday time but without this, this fabulous board is unusable because few configuration are missing like multi uart.
i hope that we will not wait too long
I second this.
A good kernel source base & config, and a good *support* for this kernel (i.e., ability to accept patches, proper efforts on bugs which users can't fix themselves, replies to users who ask about driver issues etc.) would be very important.
My own situation:
I need USB MIDI support, ALSA sound&midi support, GPIO support (for LEDs and switches).
As for now, no kernel provides everything.
The original R2 kernel has no ALSA MIDI support.
The linuxsunxi-derived 3.3-CB2 has issues with ALSA and USB (which I partially fixed myself, but still has USB issues) and little GPIO support.
The "standard" linux-sunxi-3.4 has issues with USB and GPIO.
It's a waste of time and energy to try every possible kernel and look at issues and try to resolve them myself.
I would much prefer to concentrate my efforts on my own project, or at least contribute to a *single* specific kernel to help resolving the aforementioned issues, *with support from the Olimex team*. :)
I think many other users are on my same boat.
This is a great board, I really love it! ;)
We just need to build support for it, as fast as possible, because a development board can't remain in a poorly supported state for too long, or else we end up developing for a old platform (development is, by definition, an early stage of the life of an hardware project).
Fernando
i fully agree witht this.
Putting a goodboard on the market is one thing.
Adding good support makes it a good platform.
Allot of companies need an industrial board, altough they also need to look at costs, and never will start using this board if the support is bad/costly / better at anotherplace. And there goes by your industrial grade plus!!
Everything should be freely available.
What i liked is that the datasheet is publiced now.
I couldn't agree more. Banging my head against this, with a deadline of Sept 15th.
Olimex, is there a rough ETA on posting source and config for the r2 image?
Thank you
p.s. great board!
the current release is based on Android SDK kernel with some dirty patches just to make things work, the SDK is available for download from the wiki, so you have same kernel sources
the reason we do not put the config etc patches is because we are waiting A20 GPL clean kernel to appear on Linux-Sunxi github, all changes Dimitar did are submitted there to the best of my knowledge
and soon there will be working kernel and uboot with clean GPL status for A20 on Linux-Sunxi
please be patient :)
I do not see any benefit split the kernel support in separate repos nor to put effort to develop two parallel structures while linux-sunxi is main source with the most developers
Thanks... I can't wait for this, and some clear/simple instructions on exactly how to do it ;) It's a great board waiting to be unleashed
Thank you. That makes sense. Looking forward to it.
Quote from: olimex on August 27, 2013, 10:49:08 PM
the reason we do not put the config etc patches is because we are waiting A20 GPL clean kernel to appear on Linux-Sunxi github, all changes Dimitar did are submitted there to the best of my knowledge
and soon there will be working kernel and uboot with clean GPL status for A20 on Linux-Sunxi
This makes sense, but please, the kernel developers at linux-sunxi did not test/verify a lot of issues regarding for example USB (in their words, "we just tried USB by mounting a pendrive and copying large files around").
I understand they are few and with little spare time, but of course this is absolutely insufficient for a development board, which should be the heart of vastly different projects.
So, please, could you keep an eye here on the Olimex forum, to help solving the issues of sunxi-linux kernel 3.4, which is what they are concentrated on?
That kernel has issues with GPIO, USB and Audio (just to name what I noticed first-hand) but nobody seem to care.
I can help by testing, providing debug messages and even small patches, but I need your assistance.
Please let's make A20 a 100% useful board, together. :)
Fernando
Hey all,
I see there's tons of requests for the 3.3 kernel and build instructions, I strongly urge you to refrain from using the 3.3 Kernel at all. Beyond the GPL violating reasons (on the 3.3. SDK kernel, libnand anyone) it basically is the very old 3.0.8 lychee kernel with some additions/minor fixes to support A20 hardware.
So if it has fixes (albeit minor) why shouldn't we use it? Because when linux-sunxi took the 3.0.8 kernel about a year ago, many many issues where fixed. A lot. Also upstream security issues have been merged back. The 3.0 series is now at 3.0.76 I belive? Even better, the 3.4 series is tracking the 3.4 stable from usptream, and we are very busy in merging in A20 support in.
So in matters of support, quality, stablity and security, use the 3.4 kernel from linux-sunxi. That is a kernel we can work with, support and is growing constantly. The 3.4 kernel was hosted by Hans de Goede in a seperated branch and is being merged into linux-sunxi as we speak, so give it a little time or use Hans repo.
Now if you need a very specific feature that is present in 3.3 but broken in our 3.4, that's something we should talk about and merge/fix into 3.4, a patch is always more then welcome!
Now as to the USB support, mind you, this is a cleanup of the existing USB driver, so it tries to clean up useless cruft and fix problems as they are found. If you find the pendrive test to be inssufficient, bring a bug report to the ML so those issues can be addressed. Trust me though, the 3.3 kernel is by far any better and the drivers are in far worse shape. So any test that is done, is an improvement.
So if you want better driver support/better tested drivers,use a different board with better support
But try to find one, from the Chinese SoC's linux-sunxi offers the best support, its all community driven. You can ask Allwinner for support of course ;) In this price bracket, supportwise, you are on your own.
And I don't think you can ask us developers to keep an eye out on each and every forum that produces Allwinner based hardware. Olimex produces boards based on certain chips, they 'help' you get started but on the software side, as a developer, you are on your own. If anybody finds issues, the Mailing list is the place to discus things in a true community sense.
Oliver
http://linux-sunxi.org
@oliver:
I already wrote on the linux-sunxi board, with debug outputs and all, and had no support.
Kernel 3.4, pulled from stage, has nearly non-existent USB support for MIDI keyboards. 3.3 is MUCH better so I'm using 3.3 with some patches by me.
I understand you linux-sunxi developers are busy with tons of stuff, I don't fault YOU for this: I'm asking OLIMEX, not you, to stand behind their product, following their own Olimex forum and assisting us in fixing kernel bugs TOGETHER, as in "Olimex staff and Olimex users together".
Then if the fixes find their way in linux-sunxi, much better, but I'm an Olimex customer (hopefully for more than a single developement board) and I'm mainly interested in having the Olimex board up&running, don't have much time for Allwinner boards in general.
Hope this clarifies things.
Fernando
Hi Oliver
Tanks for the information and we are very happy for all the work done by the sunxi team to have a good
kernel for Allwiner that doesn't violate GPL. Your work is very appreciate. But as Olimex customer my main concern is that i have a board that is currently useless. I already have other board from Olimex and this is the first time i have the feeling to have lost my time and my money.
I don't need a full featured kernel but have the possibility to fine tune already working feature , like more then 1 uart, i2c bus frequency, working FB console ...
I can use the sunxi kernel but there is so many branch and repository clone that this is actually a nightmare to know which one is the best for this board. I have allready try different one but was unable to have one that correspond to my need.
Regards
Philippe.
Philippe,
Linux-Sunxi community needs time to make everything properly in Kernel 3.4, please read what Oliver wrote, putting efforts to current Android Kernels 3.0 or 3.3 is waste of resources.
A20 is very new processor and as such the hardware is available in advance of proper Linux support. As you all know Allwinner cares just for Android and not Linux.
Please use Linux-Sunxi mailing list if you want to help and move things forward.
Quote from: olimex on August 28, 2013, 03:46:00 PM
Please use Linux-Sunxi mailing list if you want to help and move things forward.
Sorry but I don't think this is acceptable.
We did not purchase a "sunxi-linux" board, we purchased an Olimex board.
I'm not much interested in what the linux-sunxi community does or does not, and don't have the time to follow their busy mailing list.
I'm not a software hacker, I'm an eletronic engineer and need to use what little spare time I have to develop my own project with the Olimex board (SOC now, SOM later hopefully), not to debug kernels.
So I'd like *you OLIMEX team* to help out in ironing out the bugs in the Debian R2 distro and kernel; or at least, maybe later on, to integrate in it whatever kernel/patches/drivers the linux-sunxi community comes out with. It can't be *me* who has to follow/help out their work, because my work is to finish my own hardware project based on your (excellent, by the way) board(s).
From what I gather, this is also what other customers here are expecting: it's OK for us to cooperate with *you* to have a good support for the board, but "sunxi-linux is not our business", so to say. Maximum respect for their work of course, but that's not the point.
Fernando
Fernando, all our Allwinner based boards are because of the work done by Linux-Sunxi community, without them there would be just Android image running.
As I wrote several times above A20 is very new and this is why the Linux support is work in progress, A10, A13 etc are for more than year their support at the beginning was also not perfect but now every their feature works, thanks to Linux-Sunxi community.
Do not expect miracle from Olimex - we learn Linux also and are not expertes, we have more knowledge in electronics and help whatever we can but the real Linux work is done at Linux-Sunxi, so if you can and if you want to do contribution Linux-Sunxi mailing list is where to do this, if you want to wait somebody to clean the support just wait patiently :)
I spoke with Dimitar few minutes ago and he says he check and Linux-Sunxi Kernel 3.4 have all patches which he did to kernel 3.3. to generate image2 already merged to Kernel 3.4 tree so he now will try to build new image for Debian, Ubuntu and Slack based on Linux-Sunxi Kernel 3.4
As soon these are available I will blog how to make them and update the wiki image links, but this will not happen tomorrow after the images are build we have to test them: I2C, HDMI etc all peripherial and this is slow process.
Why it's necessary to build three different images?
I come from the Spanish board igepv2 (http://labs.isee.biz/index.php/Main_Page).
They posts uBoot source and binary, kernel source, kernel zImage and modules in a separate way.
They also provide tutorial to install debian, ubuntu etc...
Why should I download GB of new images (Debian relase 3 etc..) if I only need a new kernel image and related modules?
I agree with PaceyIV, instead of a new Debian R3 it would be great to just have a new Kernel (source and .config), when you are ready.
For example, I already did extensive modifications to Debian R2 to suit my needs (packages, symlinks, conf scripts etc.), so it's absolutely OK now, apart from the kernel.
Also, to better clarify: I have absolutely nothing against you or linux-sunxi; they are working hard on 3.4 kernel and one day we'll have a working kernel; that's great.
My point is, that we Olimex customers should not be asked of tracing what the linux-sunxi community is doing: if some of us can/want to help their work, great, but I think we should see the result of their work here on this forum/wiki.
I mean, in my opinion you should at a certain point "present here" a stable milestone of their ongoing work.
Because frankly, as Philippe said, trying to keep in sync with the maze of branches, special versions etc. of their codebase is too daunting and time-consuming for a final customer who just needs a more-or-less working kernel.
Just try a "git branch -a" on their repository, and you'll see what I mean.
Again, I'm not criticizing their work, it's just a *very different job* from what I want to do with your boards.
Moreover: say I come out with a fix for a certain driver.
It's one thing to discuss the matter here, in a relaxed way, with one of your team, and then if needed, that Olimex guy could "properly" submit a "proper" patch to the sunxi mailing list.
But trying to interface directly the list maintainers, it's too much effort for me: I would certainly give up, because of the inherent difficulties (format, code style, iter to be followed, etc.).
Fernando
Quote from: olimex on August 28, 2013, 06:19:57 PM
I spoke with Dimitar few minutes ago and he says he check and Linux-Sunxi Kernel 3.4 have all patches which he did to kernel 3.3. to generate image2 already merged to Kernel 3.4 tree so he now will try to build new image for Debian, Ubuntu and Slack based on Linux-Sunxi Kernel 3.4
I tried the stage/sunxi-3.4 and what you say isn't totaly true, ts is not working, till now i am unable to have lcd terminal working.
May be this only configuration issue but then provide minimum information to use the sunxi tree.
I, my point of view as Olimex customer this not the sunxi team that should take care of this but Olimex.
I can agree that you are not developper and that you concentrate your self on the electronic part. But then it will be nice that you clearly put on on your shop that this board is not ready to be used and that customer should best buy A10 or A13 board if they want to do something usefull.
Regards
Philippe.
+1 for information about the sunxi tree and configs used. Definitely include /proc/config.gz with the next kernel and in addition to the images (very happy about the Slackware one) - publish the compiled kernel and modules too.
I am also working on a deadlined-project, so in addition to supported features a list of missing kernel features (or todo list) on the product page will avoid many problems for both you and customers.
If one doesn't need a 'todo feature' he/she will just ignore it or otherwise ask about expected timelines.
If there is a frequently demanded 'todo feature' support questions - you will get information on what to best put your limited time on, in order to please more customers, so it's a win-win.
Please do not accept this as critics, but merely as suggestion for improvement. I am very happy with the product I bought and hope to order much more soon, when my project is completed.
Keep up the good work!
Quote from: PaceyIV on August 28, 2013, 07:10:11 PM
Why it's necessary to build three different images?
because most of our customers do not have knowledge to build linux from sources :) like us 12 months ago
having image which could be simple burned on SD card is easiest way for one to get started
...and still there are people who find it difficult to burn the image to SD card - read the forum, then imagine these people to build linux kernels and modules
Quote from: XFer on August 28, 2013, 11:51:47 AM
@oliver:
I already wrote on the linux-sunxi board, with debug outputs and all, and had no support.
Kernel 3.4, pulled from stage, has nearly non-existent USB support for MIDI keyboards. 3.3 is MUCH better so I'm using 3.3 with some patches by me.
I saw your mail, possibly while working through a 800 mail backlog after a week of vacation. To summarize, the 3.4 USB driver IS the exact same driver with bug fixes, so saying that 3.3 is MUCH better is extremly strange. Maybe you HAVE found a regression! That's bad, but the #linux-sunxi or ML is your best shot. Know that only arokux has experience with the USB driver at this very moment. He is cleaning it up etc so he can get a short at trying to mainline it. His changes only landed yesterday in the linux-sunxi kernel, before it was only in hansg's repository. So you should have pretty much the same USB driver as before ;)
Quote
I understand you linux-sunxi developers are busy with tons of stuff, I don't fault YOU for this: I'm asking OLIMEX, not you, to stand behind their product, following their own Olimex forum and assisting us in fixing kernel bugs TOGETHER, as in "Olimex staff and Olimex users together".
Then if the fixes find their way in linux-sunxi, much better, but I'm an Olimex customer (hopefully for more than a single developement board) and I'm mainly interested in having the Olimex board up&running, don't have much time for Allwinner boards in general.
Hope this clarifies things.
Fernando
I don't think you can expect this from Olimex with a 45E dev board. You should think of it more like 'here, we sell you a board, just so you can verify the hardware should work, we pre-installed this testing image we got from the Allwinner SDk. Good luck with your purchase'. If you want software support, you either have Allwinner, or buy a devboard from them. But prepare to to fork up 3000 USD or more for 'just' a dev board.
They sell you a bare board and 'help' a bit with the software, they don't offer full support on the software, that's not even really under their control.
I'm really looking forward to getting my A20 board working fully for my requirements. As mentioned before, it's a great board, but it's not well supported or documented yet. When it is better, I'd like to ditch my r-pi's and replace them with more of these.
I've been using Linux on PC's, Sun workstations, industrial/consumer products and raspberry-pi's since 1994. In the past I've built kernels on PC's. I'm not an expert, but I'm definitely not a beginner, and for the first time I'm struggling!
After too many late nights and hours wasted, I still don't fully understand where to get the correct source/patches/instructions, to build the kernel on my A20...
This isn't a complaint, I'm really hoping the feedback will help make the product successful. :)
Quote from: PaceyIV on August 28, 2013, 07:10:11 PM
Why it's necessary to build three different images?
I come from the Spanish board igepv2 (http://labs.isee.biz/index.php/Main_Page).
They posts uBoot source and binary, kernel source, kernel zImage and modules in a separate way.
They also provide tutorial to install debian, ubuntu etc...
Why should I download GB of new images (Debian relase 3 etc..) if I only need a new kernel image and related modules?
Well firstly, because you need 1 u-boot per architecture right now, so u-boot-sun4i; u-boot-sun5i and u-boot-sun7i. Then it needs to be compiled with memory timings build in (for now). Same for the kernel, it's a multi-platform kernel, but works on either sun4i or sun5i or sun7i. Development moves so quickly, that having pre-build binaries is messy, but we used to have daily built stuff at dl.linux-sunxi.org.
Once stuff slows down a bit, it's worthwhile to have precompiled stuff. But with the sunxi-bsp it's really easy to compile stuff for your platform. Warning: The BSP might not work fully due to changes with u-boot right now.
Quote from: oliver on August 28, 2013, 09:43:09 PM
Quote from: PaceyIV on August 28, 2013, 07:10:11 PM
Why it's necessary to build three different images?
[...]
Well firstly, because you need 1 u-boot per architecture right now, so u-boot-sun4i; u-boot-sun5i and u-boot-sun7i. Then it needs to be compiled with memory timings build in (for now). Same for the kernel, it's a multi-platform kernel, but works on either sun4i or sun5i or sun7i. Development moves so quickly, that having pre-build binaries is messy, but we used to have daily built stuff at dl.linux-sunxi.org.
It's not what I meant.
It isn't necessary to build a new SD card image for Debian release 3, a new image with Ubuntu and a new one with Slack for the Olimex A20 board. We're talking of Olimex A20 board: we are in this section of forum. We don't interesting about sun4i, sun5i or other platform.
I understand why Olimex do this for newbie, but if they (newbies) have already put something in the rootfs, why they should lost this work with an entirely new SD card image? For what? Just a kernel update?
It would be nice if Olimex posts the SD card image as a starting point for new users, but also the compiled uImage and a zip with modules and source code with the config. Every users should be able to substitute a file in the microSD (the uImage) and extract a file into the root path (the modules zip).
Quote from: oliver on August 28, 2013, 09:30:45 PM
Know that only arokux has experience with the USB driver at this very moment. He is cleaning it up etc so he can get a short at trying to mainline it. His changes only landed yesterday in the linux-sunxi kernel, before it was only in hansg's repository. So you should have pretty much the same USB driver as before ;)
Sorry, this does not make any sense.
With 3.4, none of my MIDI keyboard is recognized, regardless of the USB port I connect to.
With 3.3, after a few fixes (which I don't know how to apply to 3.4 because the whole USB tree is different), I get 1 MIDI keyboard correctly working, on every USB port (and this is with Hans saying I should not use the OTG mini-USB port...).
Quote
I don't think you can expect this from Olimex with a 45E dev board. You should think of it more like 'here, we sell you a board, just so you can verify the hardware should work, we pre-installed this testing image we got from the Allwinner SDk. Good luck with your purchase'
NOT-AT-ALL.
They sell a "OLINUXINO" board, the board MUST work with a Linux of sort.
Here in the EU, we have customers' rights.
But I'm not worried, I'm sure we'll get a working Linux in the end, sooner or later (hopefully sooner).
Fernando
https://github.com/hehopmajieh/OLinuXino-A20
in above repo are instructions how to build Kernel 3.3 (used in R2) and 3.4 which we use in the new image build we prepare
Note: Kernel 3.3 is based on Android SDK Kernel and may contain GPL violations which are behind our control, it's not recommended to use it nor to improve/contribute to it for development and improvement please stick to Linux-Sunxi community Kernel 3.4, which have everything working except the LCD touchscreen. We look into the TS issue to solve.
Thanks a lot i will try to stay with 3.4
Quote from: olimex on August 29, 2013, 06:47:43 PM
https://github.com/hehopmajieh/OLinuXino-A20
in above repo are instructions how to build Kernel 3.3 (used in R2) and 3.4 which we use in the new image build we prepare
Note: Kernel 3.3 is based on Android SDK Kernel and may contain GPL violations which are behind our control, it's not recommended to use it nor to improve/contribute to it for development and improvement please stick to Linux-Sunxi community Kernel 3.4, which have everything working except the LCD touchscreen. We look into the TS issue to solve.
Hmm, when i bought the device, i thought that a board called olinuxino is built with linux in mind. It would be more appropriate to call it androidino.
What about opengl support or vpu decode, can we expect it to be available in the future ?
(Hope it did not sound impolite, i know that a sub 50€ board will never be perfect).
I am not cross compiling (using the A20 with remote drive over the network) and hence no ARCH and CROSS_COMPILE flags are provided, but i get an error during compilation:
block/partitions/sunxi_nand.c:7:22: fatal error: plat/mbr.h: No such file or directory
compilation terminated.
and
drivers/ata/sw_ahci_platform.c:42:29: fatal error: plat/sys_config.h: No such file or directory
compilation terminated.
tried adding CFLAGS="-I_full_path_to_plat" to make, but still the same error ... any suggestions?
EDIT: Ahhh compiling the wrong branch ... starting over :(
EDIT 2: Not to increase the number of posts
I've got another error while native compiling:
/usr/src/linux-sunxi/arch/arm/mach-sun7i/pm/standby/mem_printk.c:168: undefined reference to `memcpy'
... used the fix to char* posted here http://irclog.whitequark.org/linux-sunxi/2013-07-14
Quote from: Tom on August 31, 2013, 03:36:45 AM
Hmm, when i bought the device, i thought that a board called olinuxino is built with linux in mind. It would be more appropriate to call it androidino.
What about opengl support or vpu decode, can we expect it to be available in the future ?
(Hope it did not sound impolite, i know that a sub 50€ board will never be perfect).
Well the olinuxino runs linux just fine, it supports the 3.4 kernel just fine, not all drivers are ported yet of course, but this is work in progress and takes time. There's only a very few of us.
Android is also still linux :)
Having said that, I would expect that anybody buying this board, just to run linux, knows to do a little research before of what works and what doesn't. But even so, just going in knowing nothing, it does work and work well.
OpenGL support is being worked on by Luc Verhagen (libv) and Connor Abbot (cabbot) and is progressing VERY nicely!!
VPU support is being worked on by a lot of people and the first status report is jpeg, mpeg12 and h264 actually working without any binary blobs.
http://linux-sunxi.org/Reverse_Engineering/Cedar_Status
Mainlining support is progressing, albeit slowly, mostly due to lack of manpower.
And here is where most developer resources go into. Migrating and mainting 3.4 kernels is 'as needed' basis. Lack of time mostly.
Can any of this be blamed on Olimex? How?! They sell you an allwinner board for developers and hobbiests. The product they sell, is a PCB with chips on it, not a full featured computer. For convienience they supply some images, but that does not go with the product!
Is this the best place to report bugs for 3.4 kernel?
There is a bad symlink in ./arch/arm/mach-sun7i/include/mach - sys_config.h points to ../plat/sys_config.h
As the link is used only in:
./drivers/net/wireless/rtl8189es/os_dep/linux/usb_intf.c
and
./drivers/gpu/mali/mali/platform/ca7-virtex820-m400-2/mali_platform.c
i think it is better to change the .c files and remove the symlink completely.
definitly not! linux-sunxi have mailing list which all developers read and this is the best place to report bugs
Quote from: olimex on August 28, 2013, 06:19:57 PM
I spoke with Dimitar few minutes ago and he says he check and Linux-Sunxi Kernel 3.4 have all patches which he did to kernel 3.3. to generate image2 already merged to Kernel 3.4 tree so he now will try to build new image for Debian, Ubuntu and Slack based on Linux-Sunxi Kernel 3.4
As soon these are available I will blog how to make them and update the wiki image links, but this will not happen tomorrow after the images are build we have to test them: I2C, HDMI etc all peripherial and this is slow process.
Do we have an update on this?
:)
please read the post on the previous page!
Quote from: olimex on August 29, 2013, 06:47:43 PM
https://github.com/hehopmajieh/OLinuXino-A20
in above repo are instructions how to build Kernel 3.3 (used in R2) and 3.4 which we use in the new image build we prepare
You mean this?
Quote from: olimex on August 29, 2013, 06:47:43 PM
please stick to Linux-Sunxi community Kernel 3.4, which have everything working except the LCD touchscreen. We look into the TS issue to solve.
But what about this? We absolutely need the touchscreen working.
How is Olimex coming with the new images and/or patches to get the touchscreen working on Kernel 3.4?
touchscreen is fixed in Kernel 3.4
Quote from: olimex on September 09, 2013, 10:17:24 AM
touchscreen is fixed in Kernel 3.4
Yaaaay!
Now I get to compile my own kernel.
we are preparing blog post with all settings
Hello, I have compiled it without problems, and put it on my R2 with modules and firmwares, but nothing happened. Card won't boot.
I have missed something ?
EDIT:
With Putty,
Quote
...
<5>Linux version 3.4.43+ (joachim@media-center) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu) ) #1 SMP PREEMPT Sun Sep 8 15:04:02 CEST 2013
CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Error: unrecognized/unsupported machine ID (r1= 0x00000f35).
Error: unrecognized/unsupported machine ID (r1= 0x00000f35).
Available machine support:
ID(hex) NAME
Available machine support:
ID(hex) NAME
000010bb sun7i
000010bb sun7i
0000102a sun5i
0000102a sun51
00001008 sun4i
00001008 sun4i
Please check your kernel config and/or bootloader.
Please check your kernel config and/or bootloader.
So on compilation, it use my desktop information rather the "CONFIG_ARCH_SUN7I=y" on config file?
# setenv machid 10bb
# saveenv
# reset
Apparently, this occurs by a change in the file mach-types in the path linux-sunxi-sunxi-3.4/arch/arm/tools
...
sun7i MACH_SUN7I SUN7I 4283
...
sun7i -> 4283 => 0x10BB
Regards,
Pinnchus
Quote from: olimex on September 09, 2013, 05:30:31 PM
we are preparing blog post with all settings
I am very much looking forward to it!
Thanks Pinnchus, with the first post it run.
The second, I have test, but 0x10BB is only 4283 in hex.
I also see on the defconfig...
OK for IS NOT SET
OK for ...=y
but what is ...=m ? I don't find word for this M
M means yes but as a module
Regards,
Pinnchus
Quote from: Black_Wolf on September 10, 2013, 10:58:48 PM
Thanks Pinnchus, with the first post it run.
The second, I have test, but 0x10BB is only 4283 in hex.
I also see on the defconfig...
OK for IS NOT SET
OK for ...=y
but what is ...=m ? I don't find word for this M
Quote from: tlhingan on September 10, 2013, 09:35:53 PM
Quote from: olimex on September 09, 2013, 05:30:31 PM
we are preparing blog post with all settings
I am very much looking forward to it!
patience :) just RTL8188CU works unreliable now, all other things are tested and work
apparently kernel 3.4 have no RTL8188CU support and Realtek drivers work with problems
Quote from: olimex on September 11, 2013, 02:51:01 PM
patience :) just RTL8188CU works unreliable now, all other things are tested and work
apparently kernel 3.4 have no RTL8188CU support and Realtek drivers work with problems
Keep it coming!
:)
Quote from: olimex on September 11, 2013, 02:51:01 PM
patience :) just RTL8188CU works unreliable now, all other things are tested and work
apparently kernel 3.4 have no RTL8188CU support and Realtek drivers work with problems
Yes, there is problem with it.
I had an USB Ralink WiFi at hand and it worked like a charm, but not the WiFi module with RTL8188CU.
Even with the 3.3 kernel from r2 it was detected (as two adapters actually), but didn't connect to my AP with WPA2, but with different one (still with WPA2) it worked.
I don't remember which one was with AES or TKIP only and which one was with both TKIP+AES and both of them where reset after that, but i can retest if it can help.
EDIT: And does SPI work with 3.4 as i need it for my project and it is the reason for moving to RPi for now.
1 month passed, and still the latest Olimex-provided 3.4 kernel has serious issues with USB support.
[ 308.267198] ehci_irq: port change detect
[ 308.337481] The port change to OHCI now!
[ 308.660384] usb 3-1: new full-speed USB device number 38 using sw-ohci
[ 308.873917] ehci_irq: port change detect
[ 308.899292] usb 3-1: USB disconnect, device number 38
[ 309.327367] ehci_irq: port change detect
[ 309.387276] The port change to OHCI now!
[ 309.710051] usb 3-1: new full-speed USB device number 39 using sw-ohci
[ 309.905040] ehci_irq: port change detect
[ 309.969253] usb 3-1: USB disconnect, device number 39
[ 310.357256] ehci_irq: port change detect
[ 310.417310] The port change to OHCI now!
Always (didn't) worked like that, since the beginning of 3.4 work, as already stated multiple times here and on the "sunxi-linux" board.
And, again as already stated multiple times, this is a regression from 3.3, because 3.3 at least recognized (briefly) the keyboard and created a proper entry and MIDI Input Device.
And, no, I won't bother writing about this on the "sunxi-linux" board again.
But now, at least, we have Olimex kernel-building instructions on the Wiki, Olimex patches for 3.4 kernel, Olimex .fex and a Olimex defconfig.
I appreciate that, honestly: it means Olimex committed to the product. Then things may or may not work, but at least Olimex worked on it and I appreciate it.
Fernando