Re: [linux-sunxi] Re: Directions for video engine support (CedarX)
>On Tue, Mar 17, 2015 at 1:22 AM, Simos Xenitellis < simos.li...@googlemail.com> wrote: >On Mon, Mar 16, 2015 at 5:35 PM, Stefan Monnier > wrote: >>> The way I understood all these was that there are short-term and >>> long-term goals for better support with the video engine. >> >> As an end user, I think that having mainline support (not just for the >> kernel, but the rest of the stack as well) for something like Kodi (nee >> XBMC) would be great. >> >> Ever since the first Android TV sticks came out, I have hoped to use one >> of those beasts as a media-center. But so far I haven't been able to do >> that: when using GNU/Linux the video playback sucks for lack of VPU >> support, and when using Android I'm faced with the problem that there's >> no DVD player software available in Android (there are lots of players >> which advertise support for playing DVDs, but they actually don't >> support playing from an optical drive). >> > >In Android, the Android image would need to implement the MediaCodec >(as in http://developer.android.com/reference/android/media/MediaCodec.html ) >class for CedarX in order to provide support for hardware >decoding/encoding to the apps. > >It's "MediaCodec" in Anrdoid 4.1 or newer. >It was "Stagefright" in previous versions of Android. I wonder it's not the appropriate place to talk about Android. The Android media interface has already implemented with hardware decoding, and it should work out of box. > >In terms of Kodi for Android, if MediaCodec is configured properly for >the Allwinner SoC, >then Kodi should work out of the box. I have tested Kodi on Android. It relies on openmax, not the media interface, as far as I know. >It should be possible to retrofit the libvdecodec.so/libvencoder.so libraries >(found on https://github.com/allwinner-zh) into an existing Android image >in order to get MediaCodec working properly for Kodi. > >Quink, do you have any instructions for that? > >Simos > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: Directions for video engine support (CedarX)
You can mount the optical drive manually. On Mon, Mar 16, 2015 at 11:35 PM, Stefan Monnier wrote: > > The way I understood all these was that there are short-term and > > long-term goals for better support with the video engine. > > As an end user, I think that having mainline support (not just for the > kernel, but the rest of the stack as well) for something like Kodi (nee > XBMC) would be great. > > Ever since the first Android TV sticks came out, I have hoped to use one > of those beasts as a media-center. But so far I haven't been able to do > that: when using GNU/Linux the video playback sucks for lack of VPU > support, and when using Android I'm faced with the problem that there's > no DVD player software available in Android (there are lots of players > which advertise support for playing DVDs, but they actually don't > support playing from an optical drive). > > > Stefan > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: What open source community is this?
I'm an employee of allwinner, and I joined this mailing list before joined the company. I speak for myself here. I have a Cubieboard2 (I bought it to do real-time vibration control as a graduate students.) runing Linux and want to playback video on that, and I saw some people have the same idea too. I want to find a workable solution, that's all. So, if we can get all of the source code from allwinner, and work out the complete open source solution, that is the best. If we can't, I want to find out just a workable solution. The graphic card AMD radeon 545v didn't work well with open source driver until Linux kernel 3.13. Before that, I have to use my laptop too, with AMD private driver. It seems that no one takes the cedar binaries as a solution, no matter whether it has been cleaned of not. If Cedrus is the only workable solution, I will try to figure out how to contribute to this project. On Mon, Mar 16, 2015 at 5:03 AM, Manuel Braga wrote: > On Sun, 15 Mar 2015 23:51:03 +0800 Quink wrote: > > Sorry Simos, I just want to invite some students in local community > > to join sunxi > > and take part in GSOC. > > And everyone are welcome to join sunxi. And the GSOC idea is not bad, > please do invite students. > > > That email has nothing to do with the CedarX. > > It's so sad that there are so many misunderstand. If we have more > > I agree, let's resolve this misunderstanding. > Simos for whatever reason, still didn't make public what he wrote to me > in our private exchange. And this is making me suspicious. > > Maybe you Quink, could help here. > By telling, who are you?, and your connection to allwinner?, if any. > What is you want to do? > And, what kind of help are expected from linux-sunxi? > > > > tolerant attitudes, technical discussing should not become a > > flashpoint, and we can be more > > Your technical question that was made in your last email is unanswered > because was part of an email that started with a "flashpoint". > Let's keep the technical discussing, separated from "flashpoints". > > > open too. > > Yes, let's all be open. > > -- > Manuel Braga > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: What open source community is this?
Sorry Simos, I just want to invite some students in local community to join sunxi and take part in GSOC. That email has nothing to do with the CedarX. It's so sad that there are so many misunderstand. If we have more tolerant attitudes, technical discussing should not become a flashpoint, and we can be more open too. On Sat, Mar 14, 2015 at 2:14 AM, Manuel Braga wrote: > On Fri, 13 Mar 2015 19:31:47 +0200 Simos Xenitellis > wrote: > > On Fri, Mar 13, 2015 at 7:11 PM, Manuel Braga > > wrote: > > > Hi. > > > > > > What open source community is this? > > > When others decide at our back, don't say what are their plans, and > > > ask us to help them, and then expect us to accept the result. > > > > > > Simos, i am repented to have answered to your private emails asking > > > for help. I did in good fate, in the hopes that we all could > > > collaborate (not fight) to create great software for this hardware. > > > > > > In that private exchange, i repeated multiple times that technical > > > discussing should be made in public, but Simos i see nothing. > > > > > > > > > And is not nice to find this. > > > https://groups.google.com/forum/#!topic/szdiy/goBZ5nZOEbU > > > (And no, is not a "GEM" driver, what is need, as i said to you, and > > > explained forward) > > > If this was the plan, why not present this in mailing list. > > > > > > Why this behavior, why this secretism, where is the "open"? > > > I don't understand. > > > Why don't you write in this mailing list, what you writed to me, > > > and go directly to the point. > > > > > > > > > Simos, one last thing. > > > With binaries blobs, you will no get the proper driver that you > > > wish. > > > > > > > Fuck my life.[non-native speakers: it's an expression like "what > > have I done to deserve this"]. > > Also me, what we all have done to deserve all this problems caused by > this video engine. > > > > > > Manuel, you are quoting an email that I sent to Quink BEFORE I > > consulted you. In that email it says "I asked Manuel Braga for some > > input and will come back to you." > > That email shows my BEFORE knowledge. > > > > In that email I suggested to Quink to try for GSOC because his G+ > > profile mentions > > that he is either a Uni student or a recent graduate (so his > > colleagues might find it interesting). > > Odd, in our private exchange, i got the impression that you told me > that he(Quink) was someone else. Maybe you and Quink should explain > better, who is who and what do are expecting from the rest of us. > As i asked you to do, in our private exchange. > > > (By the way, i don't know how GSOC handles binary globs) > > > > He should not have forwarded my email (it's etiquette not to forward > > private mails) but anyway, I do not hold grudges. > > @Quink: We are still good. > > > > What I see here is that you have been influenced by the negative vibes > > and interpreted that mail in the most negative/wrong way. > > Is not that email. > What is negative here is the secretism floating around. And this is not > healthy for an supposed open source community. > > > > > Simos > > And i repeat again. > Why don't you write in this mailing list, what you wrote to me, and go > directly to the point. The others also have the right to know, and i > don't see what is wrong with its content, that should not be public. > > > -- > Manuel Braga > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Derailed thread
I have communicated with the author of source code of libvdecoder.so. The code has been rewrote completely, has no relationship with FFmpeg, except some function names. This is a silly mistake, but maybe it's true. Does anybody know how to prove that? If the LGPL violations of libvdecoder.so can be cleaned up, how can we use the shared library on open source sunxi kernel, and even mainline kernel? I don't what's the low level part in the kernel that libvdecoder.so depends on, a thin VPU driver and some special memory management modules? If those parts can be solved, does the cedar + openmax + gstreamor openmax plugin workable? On Tue, Mar 10, 2015 at 11:01 PM, Luc Verhaegen wrote: > On Tue, Mar 10, 2015 at 01:38:30PM +, Manuel Braga wrote: > > Hi, > > > > That was a joke mail, in response to the joke that allwinner gave us > > when allwinner added the LGPL license to source code that includes a > > binary accused of being in noncompliance. > > This was not a joke email. Its contents was very serious, and it should > be interpreted as such. Allwinner needs/needed to know what it had just > done, and that it has to fullfill its obligations. > > The fact that I did so, _after_ the facts had been often and openly > discussed, and after allwinner had been explained their obligations > countless times, does make it less than serious. > > The contents however is nothing to be laughed about. > > > > try to get the support of something like the SFC so that they can > > > evaluate the merits of pursuing. > > > And then the SFC would do the talking. > > > > I heared (but don't have the details), and this looks to be true. SFC > > or someone from SFC is aware of this issue. But maybe others can make > > this more clear. > > > > But nobody is here to sue, (why do i have to keep saying this) > > i think i can speak for all and say that we want to resolve this in a > > friendly way, but for that, there most be dialog between parties. > > Not excuse to ignore the issues. > > > > And Simos look at the news, with SFC and vmware, look at the time it > > took and no result. > > People tried talking to VMWare for 7-8 years. We have been trying to > talk to Allwinner at least since 2012 (i am sure that LKCL would be > happy to divulge his conversations with allwinner if it comes to legal > action). Allwinners case is pretty open and shut, especially since they > actively use both the kernel and uboot, and the symbols in cedar are > clearly visible. And unlike VMWare Allwinner has its _whole_ business to > lose. > > When there is any legal action, it could be a lot swifter. Perhaps > Allwinner should act quickly and do so in an all encompassing way. If > not, it stands to lose quite a lot. > > Luc Verhaegen. > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Re: Re: [linux-sunxi] how to build an linux image for A31S
If the serial port is usable, maybe you can boot into fel mode by press '2' in serial terminal and then power on the device. On Mon, Mar 9, 2015 at 1:28 PM, Code Kipper wrote: > On 9 March 2015 at 03:56, li wrote: > > Hi pere canadell, > > > > the device is http://linux-sunxi.org/VidOn_Box, but i can't find the > image > > for it. > > Best Regards, > > stone > Hi Stone > I don't think you'll have any chance of getting anything other than VidOn's > firmware onto this device without doing some serious hardware > modifications. > There is no sdcard to boot from or OTG to get the device into fel mode. > I have this hardware and I'm still trying to find a way to get it to boot > into > fel mode. For now only serial debug is possible. > BR, > CK > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Allwinner GPL violations: definitive proof.
cedarx2.0 is a refactoring of cedarx1.0. The job is finished about just three month ago and not used by most vendors yet. Some work is still needed to port cedarx2.0 to linux. The directory of cedarx2.0 in Android SDK is frameworks/av/media/liballwinner. The directory of cedarx1.0 in Android SDK is frameworks/av/media/CedarX-Projects. Most part of cedarx2.0 is open source. It's not the same situation compared with cedarx1.0. Maybe it is not a big step and not enough, it is a right direction. On Fri, Mar 6, 2015 at 2:57 PM, Siarhei Siamashka < siarhei.siamas...@gmail.com> wrote: > On Wed, 4 Mar 2015 19:56:53 -0800 (PST) > oia...@gmail.com wrote: > > > I think we need to bring this back to simple. > > Thanks for sharing your opinion. But first of all, please start > playing by the rules yourself. This is a technical mailing used by > free software developers. And the subscribers are expected to > respect "Proper conduct", as explained in the linux-sunxi wiki: > http://linux-sunxi.org/Mailing_list > > Which means making sure that you don't violate: > http://linux.sgms-centre.com/misc/netiquette.php > > And in particular, the "Make sure your lines are no longer than 72 to > 76 characters in length" rule. > > > 1) as FOSS not out to harm allwinnertech all FOSS want is > > conformance with license. > > > > Reality here the two worst laws to break as a hardware vendor > > is copyright and trademark. Serous-ally. Both you can enforce by > > customs both can cause product destruction. This is pure nightmare > > because what would happen if a developer of the work decided to take > > the customs path a stack of product for one of allwinner customers > > would get to the board be ruled as contain copyright infringing work > > then crushed. This has happened to gameconsoles and other items in > > the past. The buyer is left out of pocket. > > > > Its basically a common mistake since FOSS does not act often that > > it does not have teeth. The reality most FOSS developers know they > > have the teeth to put a company out of business so try negotiation. > > > > https://libav.org/shame.html you will notice all the ones here are > > fairly much software companies. Developers don't have very effective > > teeth to go after software companies. Also remember even if the > > infringement is preformed by a sub-company the fact its on your device > > can make that device destroyable and you will be expected to get the > > compensation out the sub company that provided you with the infringing > > software. > > As a matter of fact, Allwinner does not make devices. It makes chips. > > It is the Allwinner's customers who are making devices. And the unique > situation with (at least older) Allwinner based devices is that these > devices can be running 100% free software. Very few other hardware > vendors are able to match this level of freedom (even Intel based > devices are typically shipping with proprietary BIOS firmware). > > And by the way, I'm not sure if you paid attention to the discussion in > this thread, but there is also a reverse engineered hardware video > decoder implementation available, which is 100% free software. This > means that you don't really need to use any blobs from Allwinner to > play your video. > > And to complement the perfect software freedom, some of the device > manufacturers are even making open source hardware (if you have > ever heard about this concept). For example, you can check > > https://www.olimex.com/Products/OLinuXino/open-source-hardware > > > The reality is you are better to break patent law than trademark or > > copyright as hardware company. > > > > Something Allwinner take on board is release the source after the > > fact is an extremely bad idea. If you go to Intel and Amd you will > > notice they release the open source code before the chip ship. This > > means the chips cannot be destroyed at customs. > > The SoC chips obviously do not contain the kernel code or userland > software. > > > You are only able to catch up with the source release after the > > fact because at this stage the FOSS developers are being kind. > > Look, you have blatantly violated the netiquette rules in this > mailing list. And now you are only able to catch up with the rules > after the fact. The ignorant people like you can only get away with > their misconduct because the free software developers here are being > kind. Just be grateful that nobody suggests to get you banned yet. > > > Siarhei Siamashka the case of the firmware not using the Linux > > kernel firmware loader what promises that we will not have that happen > > again. Is there staff training to make sure this does not happen > > again. > > How can we be sure that your violation of the netiquette rules will > not happen again? > > > Siarhei Siamashka there are compliance tools. > > http://www.linuxfoundation.org/programs/legal/compliance/tools > > Are you using them. If not please start using them. If yo
Re: Re: [linux-sunxi] Allwinner documentation (hardware datasheet, user manual) for A10, A10s, A13, A20, A31, A31s
You are right. China have suffer too much from idealism. Now they come to the other way. Don't say something too beautiful to them, they don't believe that and think you are a cheater. On Mon, Oct 13, 2014 at 08:11:40AM -0700, jacky lau wrote: > I agree with you and Jhon Yi. Developing a soc is not too hard now, getting > customers is harder and more important. I hope the market will force all > China Soc company more open. But before that happen, I don't think they > will become more open. > They don't have experience in working with the open source community, if you > want > them to be more open, you need to do more communicate with them. And > remember, to them, neither the law nor the spirit of free software, but > making > money is paramount. Tell them they will get more customers, make more money > and prove it, then they will follow. > > 在 2014年10月11日星期六UTC+8下午10时53分48秒,Jon Smirl写道: > > > > On Sat, Oct 11, 2014 at 10:31 AM, jacky lau > > wrote: > > > A big client will buy thousands of chips once. Are there any relation > > > between big client and user manual publishing? No. So they don't think > > it's > > > necessary to open their private property. When you are a big client, you > > are > > > VIP, all document and source code is open to you. And if publish all > > > technical documentation, competitors will know some technical secret > > (e.g. > > > bug;) they don't want them to know. > > > Open world is beautiful, but they will not actively participate if there > > is > > > no return. Why some China soc company publish some documents and source > > code > > > now? I think this is mainly for marketing. But no matter how, VIP > > priority. > > > > Right now Allwinner is only good for tablets and STBs because > > Allwinner supplies turnkey solutions. If documentation were more open > > other applications could be developed. If customer can't get software > > working for these other applications, they won't buy thousands of > > chips. So if Allwinner wants to survive past the end of the tablet fad > > they have to start developing these other markets. Otherwise when the > > tablet fad is over it will be the end of Allwinner. > > > > You also over estimate the value of "technical secrets". What is the > > point of putting a secret h.264 encode/decode unit on the chip if half > > of your customers can't get it working? Obviously Rockchip knows how > > to make h.264 encode/decode since they have a similar unit on their > > chip. And so does Freescale, TI, ST, etc. -- there is no big secret in > > making h.264 hardware for people familiar with how to do it (hint, it > > is an ISO standard). So by keeping the documentation secret you hide > > nothing significant from your competitors and much, much worse -- you > > keep your own customers from using the hardware they bought. Think > > about it --- which is more important - hiding something form a > > competitor that they probably already know, or getting your customers > > to ship and buy more chips? > > > > Bottom line - which one brings cash in the door - secret documentation > > or getting as many customers as possible to ship? > > > > > > > > > > 在 2014年10月6日星期一UTC+8下午8时55分30秒,RFat写道: > > >> > > >> Hi Kevin, > > >> > > >> Publishing the user manuals will certainly increase Allwinner's chips > > >> popularity. > > >> > > >> I was wondering if there is a rough estimate as to when the A80's > > manual > > >> will be made available? > > >> > > >> Thanks! > > >> Raanan > > >> > > >> On Monday, September 29, 2014 12:46:53 PM UTC+3, > > ke...@allwinnertech.com > > >> wrote: > > >>> > > >>> Hi All, > > >>> > > >>> I have put the documents on github, and the url is > > >>> https://github.com/allwinner-zh/documents.git > > >>> Thanks Simos, Henrik and Luc's suggestion. And other documents will be > > >>> upated to here when released. > > >>> > > >>> > > >>> > > >>> Best Regards, > > >>> kevin.z.m > > >>> > > >>> > > >>> > > >>> From: HenrikNordström > > >>> Date: 2014-09-29 08:46 > > >>> To: linux...@googlegroups.com > > >>> CC: sh...@allwinnertech.com; Meng Zhang > > >>> Subject: Re: [linux-sunxi] Allwinner documentation (hardware > > datasheet, > > >>> user manual) for A10, A10s, A13, A20, A31, A31s > > >>> sön 2014-09-28 klockan 02:18 +0200 skrev Luc Verhaegen: > > >>> > > >>> > Why didn't someone from Allwinner send these documents in > > him/herself? > > >>> > > >>> The current person discussion the matter with Allwiner was Simos, who > > is > > >>> part of the linux-sunxi community. Allwinner sent current versions of > > >>> the documents to Simos for distribution in the community. What is > > wrong? > > >>> > > >>> Mailing the full set of documents as attachments directly to the > > >>> mailinglist is not appropriate. And for some strange and unknown > > reason > > >>> Allwinner do not appear to have a public documen
Re: [linux-sunxi] A80 mixed OS (Linux / RTOS)
Such a big plan. I just did a small project with (Real-time patch for linux kernel) + (processor affinity) + (super loop) on A20. Since A20 has two A7, a real time process can occupy a processor and leave the other for other tasks. With out a working main line kernel, it seems like you have a lot of work to do to customize the kernel. On Tue, Sep 30, 2014 at 4:46 AM, javqui wrote: > Hi, > I'm working on a couple of projects requiring the classic Micro controller > features (low power, deterministic real time processing) and the classic > UX, flexibility and functionality of Linux /android. > > Most SoCs today provide many high level external hardware interfaces (like > Camera, USB, HDMI, etc) but some projects require additional drivers and > interfaces to handle different external hardware. Usually we solve the > interconnectivity with extra MCUs, FPGAs or other specialized chip > interfaces available. > > Sometimes, we design product boards with two solutions: a Cortex A SoC > like Allwinner/rockchip/Omap series and a small MCU Cortex M like the STM32 > series, but with a powerful A80, it could change forever. > > I will receive my first Optimus board soon, and I want to customize the > kernel to create a classic Linux running on the powerful 4x A15+ GPU and > Nucleus (or Free RTOS) on one or two of the A7 of the Allwinner A80 Soc. (I > made similar kernel works with MTK SoCs in the past, but never try to run > two operating systems in the same chip at the same time) > > Both projects require continuous operation and deterministic real time > response on the low power processor(s) (RTOS on A7). > User interaction (Linux on the A15 + GPU side ) is only eventual, so > termal issues by running almost all processors at the same time > occasionally, should not be a problem. > > If anyone anticipate a significant barrier to build a kernel of this type, > please share it here, I will really appreciate. I will share the results > and evaluation test here > > Additionally I will really appreciate if someone could help me to get the > A80 user manual, (please contact me by email). Both projects require access > to low level A80 features for special hardware interfaces and the user > manual is a must for both projects and future product projects related with > the A80. I want to switch almost all my projects to Allwinner A80. > > Javqui > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: Help adding I2C child node
Make sure other devices didn't occupy the I2C bus exclusively. This is what happened on my Cubieboard2 when I trying to add a mma8451. It didn't work until I removed the HDMI module which used the same I2C bus. I'm not clear about the details. On Wed, Sep 24, 2014 at 11:27 PM, bruce bushby wrote: > Quick update in case it help somebody else. > > Big thank you to selsinork for some valuable tips and pointers. > > As it turns out, you don't need a DTS entry to add an I2C child > node/device. I removed my DTS child node entries in case they were > breaking things, booted the board and then manually added the device > and kernel driver. > > Although my driver still doesn't work, I am able to see the debug > messages which is great. > > > Shell session: First I confirm I can see and query the I2C device > using i2ctools, then instantiate the device and then load the > module...which fails, but at least explains where it's failing. > > # lsmod > Module Size Used byNot tainted > # > # > # > # i2cdetect -y 0 > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- 34 -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- 77 > # > # > # > # i2cget -y 0 0x69 0x75 > 0x71 > # > # > # > # echo mpu9250 0x69 > /sys/bus/i2c/devices/i2c-0/new_device > [ 55.362493] i2c i2c-0: new_device: Instantiated device mpu9250 at 0x69 > # > # modprobe inv-mpu-iio > [ 77.347200] inv-mpu-iio 0-0069: Unable to read axis_map_x > [ 77.352699] i2c i2c-0: inv_mpu_probe failed -22 > [ 77.357254] inv-mpu-iio: probe of 0-0069 failed with error -5 > # > > > > > Bruce > > > > > > On Sat, Sep 20, 2014 at 2:54 PM, bruce bushby > wrote: > > Hi > > > > As a hobby I've been playing with an Olimex A20-SOM and trying to > > attach a Drotek Invensense MPU9250 break out board. > > > > So far my uboot is working and I can boot my build via dhcp + nfs. I > > added the "i2ctools" to the build and I'm able to run "i2cdetect -y 0" > > and I can see my devices on i2c0 > > > > # > > # i2cdetect -y 0 > > 0 1 2 3 4 5 6 7 8 9 a b c d e f > > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 30: -- -- -- -- 34 -- -- -- -- -- -- -- -- -- -- -- > > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > > 60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- -- > > 70: -- -- -- -- -- -- -- 77 > > # > > > > > > The drotek breakout board: > > http://www.drotek.fr/shop/en/home/466-imu-10dof-mpu9250-ms5611.html > > > > includes ms5611 altimeter which is why you see address "0x34" > > > > > > A very kind Daniel Baluta provided a patched version of the "inv_mpu" > > drivers enabling them to compile for the 3.16+ kernels. (rather then > > 3.4) > > > > Now I have a module (inv_mpu_iio) that loadsbut it is not > > associated with my i2c0 "0x69" device, nor has it created any /sys > > device files: > > > > # > > # lsmod > > Module Size Used byNot tainted > > inv_mpu_iio62968 0 > > # > > # dmesg | grep inv > > [1.187348] i2c i2c-0: client [inv_mpu_iio] registered with bus id > 0-0069 > > [ 22.452739] i2c-core: driver [inv_mpu_iio] registered > > # > > > > > > First question: Does my DTS child node look ok? > > > > > > i2c0: i2c@01c2ac00 { > > pinctrl-names = "default"; > > pinctrl-0 = <&i2c0_pins_a>; > > status = "okay"; > > > > mpu@69 { > > compatible = "inv_mpu_iio"; > > reg = <0x69>; > > }; > > }; > > > > > > Something has worked because I can cat this file: > > # cat /sys/devices/soc@01c0/1c2ac00.i2c/i2c-0/0-0069/name > > inv_mpu_iio > > # > > > > This is the driver I am using: > > https://github.com/BruceBushby/inv_mpu > > > > > > "inv_mpu_core.c" ...contains the probe function: > > > > static int inv_mpu_probe(struct i2c_client *client, > > const struct i2c_device_id *id) > > { > > struct inv_mpu_state *st; > > struct iio_dev *indio_dev; > > int result, err; > > pr_debug("Invensense MPU probe started.\n"); > > > > > > > > > > Sadly I don't see any "module debug" messages.even though I've > > enabled various DEBUG in my kernel config: > > > > > > CONFIG_I2C_DEBUG_CORE=y > > CONFIG_I2C_DEBUG_ALGO=y > > CONFIG_I2C_DEBUG_BUS=y > > CONFIG_DYNAMIC_DEBUG=y > > CONFIG_DEBUG_INFO=y > > CONFIG_DEBUG_KERNEL=y > > > > > > > > > > Any ideas? > > > > > > > > Thanks > > Bruce > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this gro
回复: [linux-sunxi] Optimus Board
power off the board, connect the board via serial port, unplug the otg wire, press 2 in serial terminal, power on, the board will boot into FEL mode. plug in the otg wire, open Phoenix, done. 原始邮件 主题:Re: [linux-sunxi] Optimus Board发件人:RFat 收件人:linux-sunxi@googlegroups.com抄送:yrz...@gmail.com,raan...@gmail.comSome progress to report:I finally managed to flash the Optimus Board (OB) through the USB 3. It is done using the PhoenixSuit and without installing the USB drivers (I found all the necessary software at PCDuino8 site). Despite not managing to install the usb driver on windows the PhoenixSuit managed to communicate to the board after doing one very important step: apparently the OB does not have a FEL button and what you need to do is enter the u-boot it loads (hitting any key right on boot time) and then running a command "efex" the device will suddenly be identified on windows and bingo.PCduino site have several interesting images: an android, a linux kernel which waits to boot from an sdcard (the board will not do this otherwise - or at least I didn't managed to get it to..), and well nothing less than a UBUNTU(!) which actually works with visual interface and everything (it says it is a buggy version - but still impressive). The command line says cubie so perhaps it comes from there?? There are no sources for these images. I hope this info may be useful to some of you.On Friday, September 5, 2014 7:19:15 PM UTC+3, RFat wrote:Thanks for your reply. I still could not get any progress; I tired following the dd instruction you sent in the SDK page as well as two methods described in pcduino8 page. I also got some stuff from Merrii (as Jhon suggested). I published it in a newer post on this forum.The mmc does work once the android finish loading, so it may not be an incompatibility issue between the sdcard and the mmc controller - but who knows.I'll update if I have any news (and would appreciate any ideas..)Thanks again.On Friday, September 5, 2014 6:52:56 PM UTC+3, Jon Smirl wrote:On Fri, Sep 5, 2014 at 11:33 AM, Chen-Yu Tsaiwrote: > Hi, > > On Fri, Sep 5, 2014 at 8:44 AM, Jhon Yi wrote: >> If this doesn't work, the only solution is to ask Merrii, or at least >> let them provide one bootable sdcard then dd out the content and >> search for the position. >> >> 2014-09-05 4:55 GMT+08:00 RFat : >>> Hi Jhon, >>> >>> Thanks for your suggestion. I tried: >>> dd if=boot0_sdcard_sun9iw1p1.bin of=/dev/mmcblk0 bs=1024 seek=X >>> >>> where X = 0, 4, 8, .. > > See http://linux-sunxi.org/SDK_build_howto > >>> and the board never showed any response - it is just booting from the nand >>> (I presume..). Was this what you were suggesting? > > For me, sometimes it responds, sometimes it doesn't. > Maybe the mmc controller is picky about cards, or the I/O pins > are undervolted. Without a user manual and schematics ATM, > it is hard to tell. I have had this problem on another CPU. Notes from that board 100ohm series resistor on all of the MMC lines with 10K pull ups > > When I did get a response and boot0 was loaded, boot0 then complained > it couldn't initialize mmc0, and halted. > > > ChenYu > >>> If anyone else have a suggestion - I'll be grateful >>> >>> >>> >>> On Thursday, September 4, 2014 3:01:34 AM UTC+2, Jhon Yi wrote: I suggest that you'd better ask Merrii to give you the parameters. Otherwise you could first try to dd the boot0 to a clean sd card from 8kB and see if there is any print out from the serial port (just set >>> >>> the serial port of you computer to 115200n8), if not work, move up 4kB every trial until you see the right output. Do the seem thing to uboot begin from the end of boot0, until you find something meaningful. Plus good luck. 2014-09-04 5:00 GMT+08:00 RFat : > Hi everyone, > > I just got the Optimus board (by Merrii). Seems like a nice hotrod.. > > I am trying to get u-boot running from the sdcard and I saw the > binaries: > > u-boot-sun9iw1p1.bin > boot0_sdcard_sun9iw1p1.bin > > in the SDK that poped up recently (A80_SDK_20140728). > > I guess I should be DD-ing these files to the sdcard but I am not sure > how. > There must be specific values for the seek option -- does anyone have a > clue > (I am not sure whether I am asking a trivial or a hard question..) > > Moreover, this board does not have a FEL or U-boot buttons like other > boards > - will it always look for something readable in the sdcard and then > moves on > the the nand? > > I guess everyone is very excited about the availability of these A80 > boards > and this mysterious SDK - the sunxi community is about to have crazy > power > from a crazily modest device (ah, the late 80's of Acron paid off..) > > Thanks! > > -- > Yo
Re: [linux-sunxi] Re: GPL Violations round-up
Speaking something wrong is worse than do nothing. If you are too serious about this problem, Aw will keep their mouth tight. Relax and try to communicate with them. Maybe Aw has made some improvements that we didn't know. Just blame his students is not a good teacher. On Thu, Aug 28, 2014 at 9:35 PM, Stefan Monnier wrote: > > So please stop attacking AW in this way. > > FWIW, I agree with Luc that it's important to bring this up and make > sure that there's some positive movement on that front. > Even if it's limited to splitting the blob into a "Free" glue code > linked to a binary blob. > > And it doesn't have to get all fixed right away before we can do > anything else. But there's a need to establish some understanding > between the two parties about this issue. > > > Stefan > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Getting Linux
What operating system do you have on your PC? The other partition is in the format of ext3/ext4. On Sun, Aug 10, 2014 at 1:15 AM, wrote: > Hi, > > I recently bought a Jesurun A19 Android media player that is based on the > Allwinner A20 SOC. > > I would like to run either Linux or the stock android ROM from an SD card. > However, I'm struggling to make progress. > > Here's what I've done so far: > > I tried various SD Card bootable Linux distributions build for the > Cubieboard. I eventually found one (Cubieez) that (mostly) works with the > Jesurun A19. However, networking (both wired and wireless) doesn't work. > > I did however, manage to extract the stock android image from the internal > NAND chip by running dd on the Linux command line. > > I then tried flashing the image to an SD card. When I put the SD card in a > PC, it recognises and mounts the first partition (which appears to be in > FAT format). This has enabled me to access various boot files including > script.bin. > > Unfortunately, I cannot access any of the other partitions. As far as I > can tell, the image doesn't have a standard partition table. > > I tried replacing the cubieez script.bin with the script.bin file that I > extracted from the stock Android image. However, networking still isn't > working. > > I'm rapidly running out of ideas. Can anyone help? > > Thanks, > > Jason > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.