Re: [linux-sunxi] sunxi-3.4 display driver dpms bug?
Isn't that expected? The last command turned it off, did you try turning it back on? On Jul 24, 2014 7:04 AM, Jens Thiele ka...@karme.de wrote: if I do: P=/sys/devices/platform/disp/graphics/fb0/blank echo 4 $P; echo 4 $P sleep 1 echo 0 $P the display is switched off and i can't switch the display on anymore can someone confirm? -- 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] Current state of a31 kernel
Hello, I'm not too up to date on the mainlining efforts. However I had success with the a31 running Linux. The GPU worked under mer and I managed to get Ubuntu touch booting. It did have problems but it ran. I posted some of this on my github but I haven't looked at it in almost a year. I think the A31 will work well for you but you probably won't find much help in the community. Thanks. --Neal Peacock On Jul 4, 2014 2:10 AM, uli.ra...@gmail.com wrote: Hi, Since quite some time I have been giving courses on embedded system and lately using a10 tablets for this purpose. I am now considering to switch to the a31 but I would need to know if the kernel and drivers are already in a usable state as the sunxi page on the a31 states: Proper Linux support now difficult for A31 due to the Power VR GPU Could you please update me on current developments or tell me where I can find further information. For your information: I am currently trying to install Ubuntu Touch on an a10 tablet. The kernel boots and shows its messages on the touch screen but the system crashes still rather early in the initialization phase. However... I am making progress. Thanks Uli -- 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: New board: Merrii M2 (A20)
Quick tangent, what's NDH stand for? Thanks On Mar 18, 2014 9:55 PM, Luc Verhaegen l...@skynet.be wrote: On Mon, Mar 17, 2014 at 04:49:14PM -0700, abell...@rioservice.com wrote: Hi, I bought two of these boards and am trying to make them work with Linux. Did you copy the modified u-boot into the Nand or are you booting the system from the SD Card ? Did you changed anything on the kernel/root file system ? What about the drivers ? Is everything working fine (SATA, USB, Ethernet, WIFI/BT, etc) ? Regards, Antonio Belloni Em sexta-feira, 14 de fevereiro de 2014 16h00min39s UTC-2, Marcos Cruz escreveu: Hi, This is a digital signage board based on A20 SoC, here the website: http://www.merrii.com/en/detail.asp?id=157 I managed to modify and install the Cubian distribution to function on it but I'm having problems with its VGA and HDMI outputs (no signal). The file dmesg_output contains the kernel output. What is curious about the board is I had to modify script.fex file in order to make the built in rtl8188etv operational but with the Android that comes pre-installed everything works. Have anyone any idea about the VGA and HDMI outputs? Regards, Marcos http://linux-sunxi.org/index.php?search=merrii says: There were no results matching the query. Same thing for: http://linux-sunxi.org/index.php?search=m2 I think http://linux-sunxi.org/New_Device_howto has been thrown in already. Let me paste some excerpts: I don't care about any of this, make my device work. Linux-sunxi is a community, and it is mostly peoples spare time that is sunk into it. Only very few people here work for hardware manufacturers. So no-one here has an obligation to help you. By not working through this guide, you effectively tell the people behind sunxi that they should waste their time on helping you, and only you, and that you will then plan to run off without giving even a tiny bit of time back. Why would anyone then spend their time helping you? NDH, or you're on your own. 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: [linux-sunxi] Livesuite image building tools
Last time I tried the sunxi-bsp tools they weren't working and I didn't see much interest in fixing them (myself included). The lichee tools are going to have no support unless you buy a Dev kit from wits but wits is actually very helpful if you do. I had the Lichee tools for a31 and they worked very well. I haven't tried them for other chips. Either way though you are probably on your own though so I would just experiment. On Apr 6, 2014 1:17 PM, beat...@beattie-home.net wrote: I'm trying to get build root to build an image that I can flash into my Cubieboard2 and boot. I think this means an image that Livesuit (which I have working) can read. It looks like sunxi-bsp is the preferred solution for building Livesuit images around here. I think I have buildroot building all of the u-boot files I need, and from looking at sunxi-bsp it looks like what I need mostly at this point is linux-sunxi/allwinner-tools from github (which is mostly proprietary binaries). I have also noted that there seems to be a newer toolset (from allwinner?) under the name Lichee? Is the linux-sunxi/allwinner-tools the way to go, or is there another way to build a Livesuit image from scratch? Also what do people think of the lichee toolset. Brian * https://github.com/linux-sunxi/allwinner-tools* -- 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] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Answers in line. Thanks
On Mar 9, 2014 11:34 AM, hunter hu hunterhu...@gmail.com wrote:
Hi Neal,
Thanks for that.
I have no idea about the magic signing value, I have 3 questions and
comments:
1 If I just use the original nandb.img which was dd out of the nand
itself, will that still be needed?
No but I think you will have to change at least one parameter. I've got to
find my notes on it..
2 if I do create a magic signing value again, how would I do that?
Its in the tools directory of a linux-sunxi u-boot repo.
https://github.com/linux-sunxi/u-boot-sunxi/blob/sunxi/tools/mkenvimage.c
Again I've got some notes somewhere on how to use it.
3 would this why my previous lichee-dev u-boot.bin doesn't play well
with boot0/boot1? did I miss any magic value there?
There is a uboot signer in tools as well so maybe. When booting from band
I stuck with the included Android u-boot.
Thanks,
-Hunter
On Sunday, March 9, 2014 1:25:42 PM UTC-5, npeacock wrote:
Hello,
Seems like the structure was
/dev/nandb u-boot.env with magic signing value
/dev/nandc the linux kernel, just dd copied on, make sure to clear
with zero in case yours its smaller
/dev/nandX the root partition, which was defined in the u-boot.env, so
you could make it whatever you want, as long as it matches your env file.
If nandj is 5Gb then that is what I would use in my hacky approach.
So is that more clear? You'll need to put your linux kernel in nandc,
your adjusted uboot.env in nandb and your rootfs on a new partition on nandj
I'll try to find the actual script and old images tonight. I was having
a lot of trouble uploading large files and hadn't tried in awhile.
Thanks.
On 3/9/2014 11:07 AM, hunter hu wrote:
Hi Neal,
The link seems broken while I was trying to get the image: wget
http://pengpod.com/dl/images/pengpod1000-linaro-flashcard-2013.03.29.img.tar.gz
However, I can set things up by following the same logic, but I need to
confirm one change, for nandb, what changes need to be made? I plan to edit
binary image out from my board, there are actually 2 entries for the
environment,
one setup root=/dev/nandc
the other setup root=/dev/nandd
according to your notes, we will dd uImage into nandc, so say, if I
will use nandj (which is 5G in size) as the rootfs, should I change the
both nandc and nandd to nandj or just nandd to nandj?
Thanks,
-Hunter
On Saturday, March 8, 2014 10:54:28 PM UTC-6, npeacock wrote:
Here is a link for what I did on the PengPod where we used the
original u-boot from Android.
http://pengpod.com/pengwiki/index.php?title=Install_Linaro_to_the_internal_flash
The only trick not listed was the u-boot environment had to be signed,
I can't remember the name of the tool but its in the u-boot repo.
I think the first logo was displayed by boot1, before u-boot runs.
Hi Timo,
Thanks for the detailed answer to my questions, really appreciate
that.
I have done the same thing, still I am stuck at the logo screen,
feels like there is something else is missing in my case.
1 I don't see any serial output from NAND boot, did you see anything
on the serial console if you were using serial output?
2 anyone knows if the logo has been displayed, does it imply that
u-boot.bin got loaded at all?
I think in my case, the question is why u-boot.bin built from
sun5i_a13 with the CONFIG_BOOTCOMMAND modification doesn't print any output
at all? in the common/main.c:
205 static inline int abortboot(int bootdelay)
206 {
207 int abort = 0;
208
209 #ifdef CONFIG_MENUPROMPT
210 printf(CONFIG_MENUPROMPT);
211 #else
212 printf(Hit any key to stop autoboot: %2d , bootdelay);
213 #endif
would always print Hit any key to stop autoboot:, even if something
went wrong later? but I saw nothing from console, (UART1 that is I am using
and good with SD boot).
Still baffled, :-(
Regards,
-Hunter
On Saturday, March 8, 2014 1:07:44 PM UTC-6, Timo Schmiade wrote:
Hi Patrick,
Looks to me like this is loading script.bin and uImage from nanda.
thanks for pointing this out, you're of course right! nandb contains
my root filesystem, nanda is the boot partition.
On Sat, Mar 8, 2014 at 3:24 PM, Patrick Wood patric...@gmail.com
wrote:
Looks to me like this is loading script.bin and uImage from nanda.
--
You received this message because you are subscribed to a topic in
the Google Groups linux-sunxi group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe.
To unsubscribe from this group and all of its topics, send an
email to linux-sunxi...@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...@googlegroups.com.
For more options, visit
Re: [linux-sunxi] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Hello,
Seems like the structure was
/dev/nandb u-boot.env with magic signing value
/dev/nandc the linux kernel, just dd copied on, make sure to clear
with zero in case yours its smaller
/dev/nandX the root partition, which was defined in the u-boot.env, so
you could make it whatever you want, as long as it matches your env
file. If nandj is 5Gb then that is what I would use in my hacky approach.
So is that more clear? You'll need to put your linux kernel in nandc,
your adjusted uboot.env in nandb and your rootfs on a new partition on nandj
I'll try to find the actual script and old images tonight. I was having
a lot of trouble uploading large files and hadn't tried in awhile.
Thanks.
On 3/9/2014 11:07 AM, hunter hu wrote:
Hi Neal,
The link seems broken while I was trying to get the image: wget
http://pengpod.com/dl/images/pengpod1000-linaro-flashcard-2013.03.29.img.tar.gz
However, I can set things up by following the same logic, but I need
to confirm one change, for nandb, what changes need to be made? I plan
to edit binary image out from my board, there are actually 2 entries
for the environment,
one setup root=/dev/nandc
the other setup root=/dev/nandd
according to your notes, we will dd uImage into nandc, so say, if I
will use nandj (which is 5G in size) as the rootfs, should I change
the both nandc and nandd to nandj or just nandd to nandj?
Thanks,
-Hunter
On Saturday, March 8, 2014 10:54:28 PM UTC-6, npeacock wrote:
Here is a link for what I did on the PengPod where we used the
original u-boot from Android.
http://pengpod.com/pengwiki/index.php?title=Install_Linaro_to_the_internal_flash
http://pengpod.com/pengwiki/index.php?title=Install_Linaro_to_the_internal_flash
The only trick not listed was the u-boot environment had to be
signed, I can't remember the name of the tool but its in the
u-boot repo.
I think the first logo was displayed by boot1, before u-boot runs.
Hi Timo,
Thanks for the detailed answer to my questions, really appreciate
that.
I have done the same thing, still I am stuck at the logo screen,
feels like there is something else is missing in my case.
1 I don't see any serial output from NAND boot, did you see
anything on the serial console if you were using serial output?
2 anyone knows if the logo has been displayed, does it imply
that u-boot.bin got loaded at all?
I think in my case, the question is why u-boot.bin built from
sun5i_a13 with the CONFIG_BOOTCOMMAND modification doesn't print
any output at all? in the common/main.c:
|
205 static inline int abortboot(int bootdelay)
206 {
207 int abort = 0;
208
209 #ifdef CONFIG_MENUPROMPT
210 printf(CONFIG_MENUPROMPT);
211 #else
212 printf(Hit any key to stop autoboot: %2d , bootdelay);
213 #endif
|
would always print Hit any key to stop autoboot:, even if
something went wrong later? but I saw nothing from console,
(UART1 that is I am using and good with SD boot).
Still baffled, :-(
Regards,
-Hunter
On Saturday, March 8, 2014 1:07:44 PM UTC-6, Timo Schmiade wrote:
Hi Patrick,
Looks to me like this is loading script.bin and uImage from
nanda.
thanks for pointing this out, you're of course right! nandb
contains
my root filesystem, nanda is the boot partition.
On Sat, Mar 8, 2014 at 3:24 PM, Patrick Wood
patric...@gmail.com wrote:
Looks to me like this is loading script.bin and uImage from
nanda.
--
You received this message because you are subscribed to a
topic in the Google Groups linux-sunxi group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe
https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe.
To unsubscribe from this group and all of its topics, send
an email to linux-sunxi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout
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...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout
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
mailto: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
Re: [linux-sunxi] [A10] Getting u-boot onto freshly partitioned Nand for booting Linux
Here is a link for what I did on the PengPod where we used the original
u-boot from Android.
http://pengpod.com/pengwiki/index.php?title=Install_Linaro_to_the_internal_flash
The only trick not listed was the u-boot environment had to be signed, I
can't remember the name of the tool but its in the u-boot repo.
I think the first logo was displayed by boot1, before u-boot runs.
Hi Timo,
Thanks for the detailed answer to my questions, really appreciate that.
I have done the same thing, still I am stuck at the logo screen, feels
like there is something else is missing in my case.
1 I don't see any serial output from NAND boot, did you see anything
on the serial console if you were using serial output?
2 anyone knows if the logo has been displayed, does it imply that
u-boot.bin got loaded at all?
I think in my case, the question is why u-boot.bin built from
sun5i_a13 with the CONFIG_BOOTCOMMAND modification doesn't print any
output at all? in the common/main.c:
|
205 static inline int abortboot(int bootdelay)
206 {
207 int abort = 0;
208
209 #ifdef CONFIG_MENUPROMPT
210 printf(CONFIG_MENUPROMPT);
211 #else
212 printf(Hit any key to stop autoboot: %2d , bootdelay);
213 #endif
|
would always print Hit any key to stop autoboot:, even if something
went wrong later? but I saw nothing from console, (UART1 that is I am
using and good with SD boot).
Still baffled, :-(
Regards,
-Hunter
On Saturday, March 8, 2014 1:07:44 PM UTC-6, Timo Schmiade wrote:
Hi Patrick,
Looks to me like this is loading script.bin and uImage from nanda.
thanks for pointing this out, you're of course right! nandb contains
my root filesystem, nanda is the boot partition.
On Sat, Mar 8, 2014 at 3:24 PM, Patrick Wood patric...@gmail.com
javascript: wrote:
Looks to me like this is loading script.bin and uImage from nanda.
--
You received this message because you are subscribed to a topic
in the Google Groups linux-sunxi group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe
https://groups.google.com/d/topic/linux-sunxi/omgs3skJYDI/unsubscribe.
To unsubscribe from this group and all of its topics, send an
email to linux-sunxi...@googlegroups.com javascript:.
For more options, visit https://groups.google.com/d/optout
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
mailto: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] sun5i_csi0 Difficulties
I put in a simple patch to initialize one of the related variables on sun4i
csi. If you can find that it might be related, I never put the same fix in
for sun5i but I think it had the same problem.
On Feb 8, 2014 10:01 AM, hunter hu hunterhu...@gmail.com wrote:
Hi,
I am having a hard time to get sun5i_csi0 working on an A13 iview 435tpc
tablet running Debian 7 Wheezy.
After building and loading the new kernel image using sunxi-bsp onto the
target,
The sun5i_csi0 driver init fine:
/home/debian# modprobe sun5i_csi0
Feb 8 17:06:08 debian-armhf kernel: [ 357.074779] Linux video capture
interface: v2.00
Feb 8 17:06:08 debian-armhf kernel: [ 357.145149] [CSI]Welcome to CSI
driver
Feb 8 17:06:08 debian-armhf kernel: [ 357.146771] [CSI]csi_init
Feb 8 17:06:08 debian-armhf kernel: [ 357.186431] [CSI]registered subdevice
,input_num = 0
Feb 8 17:06:08 debian-armhf kernel: [ 357.189966] [CSI]power on andpower
off camera
!
Feb 8 17:06:09 debian-armhf kernel: [ 357.337829] [CSI]V4L2 device
registered as video0
/home/debian# lsmod
Module Size Used by
gc0308 13439 1
sun5i_csi0 30537 0
videobuf_dma_contig 7326 1 sun5i_csi0
videobuf_core 22410 2 sun5i_csi0,videobuf_dma_contig
v4l2_common 9112 2 gc0308,sun5i_csi0
videodev 81433 3 gc0308,v4l2_common,sun5i_csi0
mali 113219 0
ump35383 1 mali
But when I am actually trying to use it:
root@debian-armhf:/home/debian# fswebcam
--- Opening /dev/video0...
Trying source module v4l2...
/dev/video0 opened.
No input was specified, using the first.
Adjusting resolution from 384x288 to 640x480.
Message from syslogd@debian-armhf at Feb 8 17:10:37 ...
kernel:[ 624.775339] Internal error: Oops - BUG: 0 [#1] PREEMPT ARM
Message from syslogd@debian-armhf at Feb 8 17:10:37 ...
kernel:[ 625.236690] Process fswebcam (pid: 2400, stack limit =
0xd5a762e8)
...
The dmesg:
Feb 8 17:10:36 debian-armhf kernel: [ 624.540776] [CSI_ERR]v4l2 subdevice
queryctrl error
!
Feb 8 17:10:36 debian-armhf kernel: [ 624.544807] [CSI_ERR]v4l2 subdevice
queryctrl error
!
...(tons of the queryctrl error)
Feb 8 17:10:36 debian-armhf kernel: [ 624.716342] [CSI_ERR]v4l2 subdevice
queryctrl error
!
Feb 8 17:10:36 debian-armhf kernel: [ 624.721427] [CSI_ERR]Fourccformat
(0x4745504a) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.725739] [CSI_ERR]Fourccformat
(0x47504a4d) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.731129] [CSI_ERR]Fourccformat
(0x31363553) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.735440] [CSI_ERR]Fourccformat
(0x33424752) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.740801] [CSI_ERR]Fourccformat
(0x33524742) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.745337] [CSI_ERR]Fourccformat
(0x34424752) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.750436] [CSI_ERR]Fourccformat
(0x34524742) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.756742] [CSI]buffer_setup,buffer
count
=4, size=614400
Feb 8 17:10:37 debian-armhf kernel: [ 624.761926] [ cut
here ]
The trace:
Message from syslogd@debian-armhf at Feb 8 17:10:37 ...
kernel:[ 625.332677] 7e40: d597ca00 bf039184 000481c2 bf039454
02ecc0b9caa0
0001
Feb 8 17:10:37 debian-armhf kernel: [ 625.436157] [bf05c4d0] (
videobuf_next_field+0x30/0x34 [videobuf_core]) from [bf05c7cc] (
videobuf_qbuf+0x2f8/0x4bc [videobuf_core])
Feb 8 17:10:37 debian-armhf kernel: [ 625.446645] [bf05c7cc] (
videobuf_qbuf+0x2f8/0x4bc [videobuf_core]) from [bf03b334] (
__video_do_ioctl+0x1ee0/0x4ae4 [videodev])
Feb 8 17:10:37 debian-armhf kernel: [ 625.456753] [bf03b334] (
__video_do_ioctl+0x1ee0/0x4ae4 [videodev]) from [bf039184] (
video_usercopy+0x280/0x544 [videodev])
Feb 8 17:10:37 debian-armhf kernel: [ 625.466159] [bf039184] (
video_usercopy+0x280/0x544 [videodev]) from [bf0383ec] (v4l2_ioctl+0x134
/0x150 [videodev])
Feb 8 17:10:37 debian-armhf kernel: [ 625.474441] [bf0383ec] (
v4l2_ioctl+0x134/0x150 [videodev]) from [c00d2b94] (do_vfs_ioctl+0x3cc/
0x5cc)
Feb 8 17:10:37 debian-armhf kernel: [ 625.481491] [c00d2b94] (
do_vfs_ioctl+0x3cc/0x5cc) from [c00d2dc8] (sys_ioctl+0x34/0x60)
Feb 8 17:10:37 debian-armhf kernel: [ 625.488631] [c00d2dc8] (
sys_ioctl+0x34/0x60) from [c000ea40] (ret_fast_syscall+0x0/0x30)
Feb 8 17:10:37 debian-armhf kernel: [ 625.513930] ---[ end trace
2ea2b3b07ac67c8f ]---
The trace points to the following code snippet BUG_ON():
/* drivers/media/video/videobuf-core.c */
295 /* Locking: Caller holds q-vb_lock */
296 enum v4l2_field videobuf_next_field(struct videobuf_queue *q)
297 {
298 enum v4l2_field field = q-field;
299
300 BUG_ON(V4L2_FIELD_ANY == field);
301
302 if (V4L2_FIELD_ALTERNATE == field) {
303 if (V4L2_FIELD_TOP == q-last) {
304
Re: [linux-sunxi] sun5i_csi0 Difficulties
Never mind looks like you got a handle on it.
On Feb 13, 2014 9:42 AM, Neal Peacock kulimandpho...@gmail.com wrote:
I put in a simple patch to initialize one of the related variables on
sun4i csi. If you can find that it might be related, I never put the same
fix in for sun5i but I think it had the same problem.
On Feb 8, 2014 10:01 AM, hunter hu hunterhu...@gmail.com wrote:
Hi,
I am having a hard time to get sun5i_csi0 working on an A13 iview 435tpc
tablet running Debian 7 Wheezy.
After building and loading the new kernel image using sunxi-bsp onto the
target,
The sun5i_csi0 driver init fine:
/home/debian# modprobe sun5i_csi0
Feb 8 17:06:08 debian-armhf kernel: [ 357.074779] Linux video capture
interface: v2.00
Feb 8 17:06:08 debian-armhf kernel: [ 357.145149] [CSI]Welcome to CSI
driver
Feb 8 17:06:08 debian-armhf kernel: [ 357.146771] [CSI]csi_init
Feb 8 17:06:08 debian-armhf kernel: [ 357.186431] [CSI]registered subdevice
,input_num = 0
Feb 8 17:06:08 debian-armhf kernel: [ 357.189966] [CSI]power on andpower
off camera
!
Feb 8 17:06:09 debian-armhf kernel: [ 357.337829] [CSI]V4L2 device
registered as video0
/home/debian# lsmod
Module Size Used by
gc0308 13439 1
sun5i_csi0 30537 0
videobuf_dma_contig 7326 1 sun5i_csi0
videobuf_core 22410 2 sun5i_csi0,videobuf_dma_contig
v4l2_common 9112 2 gc0308,sun5i_csi0
videodev 81433 3 gc0308,v4l2_common,sun5i_csi0
mali 113219 0
ump35383 1 mali
But when I am actually trying to use it:
root@debian-armhf:/home/debian# fswebcam
--- Opening /dev/video0...
Trying source module v4l2...
/dev/video0 opened.
No input was specified, using the first.
Adjusting resolution from 384x288 to 640x480.
Message from syslogd@debian-armhf at Feb 8 17:10:37 ...
kernel:[ 624.775339] Internal error: Oops - BUG: 0 [#1] PREEMPT ARM
Message from syslogd@debian-armhf at Feb 8 17:10:37 ...
kernel:[ 625.236690] Process fswebcam (pid: 2400, stack limit =
0xd5a762e8)
...
The dmesg:
Feb 8 17:10:36 debian-armhf kernel: [ 624.540776] [CSI_ERR]v4l2 subdevice
queryctrl error
!
Feb 8 17:10:36 debian-armhf kernel: [ 624.544807] [CSI_ERR]v4l2 subdevice
queryctrl error
!
...(tons of the queryctrl error)
Feb 8 17:10:36 debian-armhf kernel: [ 624.716342] [CSI_ERR]v4l2 subdevice
queryctrl error
!
Feb 8 17:10:36 debian-armhf kernel: [ 624.721427] [CSI_ERR]Fourccformat
(0x4745504a) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.725739] [CSI_ERR]Fourccformat
(0x47504a4d) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.731129] [CSI_ERR]Fourccformat
(0x31363553) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.735440] [CSI_ERR]Fourccformat
(0x33424752) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.740801] [CSI_ERR]Fourccformat
(0x33524742) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.745337] [CSI_ERR]Fourccformat
(0x34424752) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.750436] [CSI_ERR]Fourccformat
(0x34524742) invalid.
Feb 8 17:10:36 debian-armhf kernel: [ 624.756742] [CSI]buffer_setup,buffer
count
=4, size=614400
Feb 8 17:10:37 debian-armhf kernel: [ 624.761926] [ cut
here ]
The trace:
Message from syslogd@debian-armhf at Feb 8 17:10:37 ...
kernel:[ 625.332677] 7e40: d597ca00 bf039184 000481c2 bf039454
02ecc0b9caa0
0001
Feb 8 17:10:37 debian-armhf kernel: [ 625.436157] [bf05c4d0] (
videobuf_next_field+0x30/0x34 [videobuf_core]) from [bf05c7cc] (
videobuf_qbuf+0x2f8/0x4bc [videobuf_core])
Feb 8 17:10:37 debian-armhf kernel: [ 625.446645] [bf05c7cc] (
videobuf_qbuf+0x2f8/0x4bc [videobuf_core]) from [bf03b334] (
__video_do_ioctl+0x1ee0/0x4ae4 [videodev])
Feb 8 17:10:37 debian-armhf kernel: [ 625.456753] [bf03b334] (
__video_do_ioctl+0x1ee0/0x4ae4 [videodev]) from [bf039184] (
video_usercopy+0x280/0x544 [videodev])
Feb 8 17:10:37 debian-armhf kernel: [ 625.466159] [bf039184] (
video_usercopy+0x280/0x544 [videodev]) from [bf0383ec] (v4l2_ioctl+
0x134/0x150 [videodev])
Feb 8 17:10:37 debian-armhf kernel: [ 625.474441] [bf0383ec] (
v4l2_ioctl+0x134/0x150 [videodev]) from [c00d2b94] (do_vfs_ioctl+0x3cc/
0x5cc)
Feb 8 17:10:37 debian-armhf kernel: [ 625.481491] [c00d2b94] (
do_vfs_ioctl+0x3cc/0x5cc) from [c00d2dc8] (sys_ioctl+0x34/0x60)
Feb 8 17:10:37 debian-armhf kernel: [ 625.488631] [c00d2dc8] (
sys_ioctl+0x34/0x60) from [c000ea40] (ret_fast_syscall+0x0/0x30)
Feb 8 17:10:37 debian-armhf kernel: [ 625.513930] ---[ end trace
2ea2b3b07ac67c8f ]---
The trace points to the following code snippet BUG_ON():
/* drivers/media/video/videobuf-core.c */
295 /* Locking: Caller holds q-vb_lock */
296 enum v4l2_field videobuf_next_field(struct videobuf_queue *q)
297 {
298 enum v4l2_field field = q-field;
299
300 BUG_ON(V4L2_FIELD_ANY
Re: [linux-sunxi] Seeking consultant for Linux-Sunxi integration project
On Jan 6, 2014 3:00 AM, Olliver Schinagl oliver+l...@schinagl.nl wrote: On 03-01-14 14:30, Neal Peacock wrote: On Jan 3, 2014 5:01 AM, Olliver Schinagl oliver+l...@schinagl.nl mailto:oliver%2bl...@schinagl.nl wrote: On 01-01-14 04:54, npeacock wrote: I am looking for someone interested in consulting work for a company using Linux on Allwinner tablets, starting immediately. To keep this thread going, What would someone have to do for this company? How many hours a week are you expected to work for them etc etc. They do not have any staff that could do this themselves? Is it really that much work that you haven't been able to do it yet yourself? The short answer is I've had zero time between relocation and family. That is also why I have been slow to respond here. An update a second company has contacted me looking for something similar so I can help arrange another job if anyone is interested. Its probably more long term work with bigger goals. I don't know much about the company though. Any other questions email me directly. Oliver I don't want to mention the company name in the open, like this, but I would be glad to share it in private email about the job. They build vending and outdoor payment systems and have come to realize buying stock tablets is cheaper, faster and generally better than their own in house designs, assuming they have the flexibility of Linux. They came to me from my experience with PengPod and I've done a little work so far. I can help pass things over to you. Basically, they are trying to bring three tablets on-line with a real Linux image (they had a chroot proof of concept running Debian inside of Android) and modify a few drivers for their needs. They have been good to work for. They are very flexible about my schedule, they already have many remote staff (some international), they are responsive to provide the tools and answers needed to move things along. I think there is probably a need for a permanent platform position in their team, helping add features and for the various future projects they have in mind. They are pretty ambitious in the long term. I've taken a permanent position with a non-compete, so I wont be able to work for them any more after the 13th. Oh, also they paid pretty well too. Anyone who is interested please let me know. I mostly need to hear about what you have done with Allwinner devices, but the company will want see a resume. I'll put you in touch directly about wages in all after we have our QA. No on site work required, test devices will be sent to you. I assume this is US Residents work only? This is open to anyone, anywhere. The company currently has mostly remote employees, several outside the US. Just inquiring. Oliver Thanks. -- Neal Peacock PengPod -- 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 mailto:linux-sunxi%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 mailto:linux-sunxi%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
[linux-sunxi] Seeking consultant for Linux-Sunxi integration project
Hello, I am looking for someone interested in consulting work for a company using Linux on Allwinner tablets, starting immediately. I don't want to mention the company name in the open, like this, but I would be glad to share it in private email about the job. They build vending and outdoor payment systems and have come to realize buying stock tablets is cheaper, faster and generally better than their own in house designs, assuming they have the flexibility of Linux. They came to me from my experience with PengPod and I've done a little work so far. I can help pass things over to you. Basically, they are trying to bring three tablets on-line with a real Linux image (they had a chroot proof of concept running Debian inside of Android) and modify a few drivers for their needs. They have been good to work for. They are very flexible about my schedule, they already have many remote staff (some international), they are responsive to provide the tools and answers needed to move things along. I think there is probably a need for a permanent platform position in their team, helping add features and for the various future projects they have in mind. They are pretty ambitious in the long term. I've taken a permanent position with a non-compete, so I wont be able to work for them any more after the 13th. Oh, also they paid pretty well too. Anyone who is interested please let me know. I mostly need to hear about what you have done with Allwinner devices, but the company will want see a resume. I'll put you in touch directly about wages in all after we have our QA. No on site work required, test devices will be sent to you. Thanks. -- Neal Peacock PengPod -- 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/groups/opt_out.
Re: [linux-sunxi] Firmware for Bluetooth (and wifi)
Sorry to not post inline, I'm on my phone but didn't want to forget to comment. Have you looked into differences in bluez between the working Android and not working Linux? On my a31 devices that was the Bluetooth fix for a similar chip set. Bluez had to support a different serial protocol if I remember right. It all took place in userspace though. On Dec 27, 2013 7:36 AM, Chen-Yu Tsai w...@csie.org wrote: Hi, On Fri, Dec 27, 2013 at 7:47 PM, Arend van Spriel ar...@broadcom.com wrote: On 12/26/2013 05:13 PM, Chen-Yu Tsai wrote: Hi, On Thu, Dec 19, 2013 at 6:12 PM, Chen-Yu Tsai w...@csie.org wrote: Hi, On Thu, Dec 19, 2013 at 12:39 AM, Chen-Yu Tsai w...@csie.org wrote: Hi, On Thu, Dec 19, 2013 at 12:16 AM, Arend van Spriel ar...@broadcom.com wrote: On 12/18/2013 02:12 PM, Hans de Goede wrote: Hi, On 12/18/2013 11:31 AM, Arend van Spriel wrote: On 12/05/2013 10:46 PM, Julian Calaby wrote: Firstly, are there any plans to support the BCM43362 chipset with the brcmfmac driver in the near future? Hi Julian, I am working on a patch to support this chip. It is looking promising. Just have to go after a firmware image to be sure. Cool. Do you have a cubietruck? With my latest wip tree: https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-next No cubietruck here. I googled the term last week because it came up and found embeddedcomputer.nl selling it. We've mmc/sdio controller support on top of 3.13-rc4, it would be nice if we could also get the wifi and bluetooth to work here. I got the chip to respond to probing. It is BCM43362 for sure. root@cubietruck:/sys/bus/mmc/devices/mmc1:0001/mmc1:0001:1# cat device 0xa962 root@cubietruck:/sys/bus/mmc/devices/mmc1:0001/mmc1:0001:1# cat vendor 0x02d0 Vendor ID is Broadcom. Device ID is 43362. But I get two devices, mmc1:0001:1 and mmc1:0001:2. I don't know if this is normal or not. There might be three devices/functions. The last digit of the device indicates the SDIO function number. Function 1 allows access to F1 registers in the SDIO core of the device and F2 is for WLAN functionality. F3 could be providing BT functionality, but I am not familiar with that part. Merry Christmas everyone. I got AP6210 (BCM43362) to work with mainline brcmfmac driver. I only tested managed mode. Monitor mode does not work. You can use firmware from CubieTech images. brcmfmac does not support monitor mode. It does support AP mode and P2P modes. Things missing: 1. output clock is using default 32KHz from 24M / 750. need to find some place to put clk_set_rate call. What clock is this? You mean there is a clock output driven by the AP6210 module or Cubieboard provides it to the module. Cubieboard provides it to the module. BCM43362 (WiFi) and BCM20710 (BT) both accept an external 32768 Hz clock as low power clock. They can also use internal oscillator for this, so it is optional. But according to BCM20710 datasheet, this external clock is required to auto-detect the frequency of the main oscillator if it's not the default 20MHz. On the CubieTruck, it is 26 MHz. For just WiFi, I think we don't need it. 2. BCM43362 out-of-band interrupts not supported. OOB interrupt in brcmfmac is set using platform data. Need to put this is board code, or add device tree support. It would be good to add device tree support so the driver can first look for device tree data and have platform data and in-band as backup mechanism. I'm not sure how to add support. Add a child node to the SD/MMC controller, perhaps? I thought SDIO devices were like USB, in that the system scans the bus and detects them. Core ID and addresses were found using bcmdhd driver debug output. Arend might want to take a look at the patch: https://github.com/wens/linux/commit/d945809d27de930eba5db0ca4bb7936e3ca88865 I have different addresses from the chip documentation, but my test spin went poorly. So much for hardware documentation. I will give these values a try. In my patch there is also bcm43362 specific SDIO drive strength programming (see attachment). The patch won't apply as my tree is a bit different due to some rework in the SDIO part of brcmfmac. So you probably need to pick the missing part from it. Maybe it's a remarked chip? (is that possible?) The firmware CubieTech has is for a BCM40181 though. Added the drive strength programming by hand. Changed the table variable name to match the others. Pushed on to my tree. Beware there are some hacks trying to get BT to work. :p Working tree: https://github.com/wens/linux/tree/wip/sunxi-next-wifi Comments welcome :) No comment, but: Nice work! Thanks. BTW, who should submit the patch? :) ChenYu Gr. AvS Bluetooth still isn't responding. Bluetooth still not working. :( Has anyone had any luck with this? I'm certainly
