On Thu, Apr 30, 2015 at 9:36 PM, William Hermans wrote:
> Seems almost as though news sites care more about Linus' "whimsical" reason
> for 4.x. Rather than what 4.x *is*. Anyhow, of all the new changes I think
> live patching would be the coolest. Except . . . it's x86 only for now. The
> other s
Seems almost as though news sites care more about Linus' "whimsical" reason
for 4.x. Rather than what 4.x *is*. Anyhow, of all the new changes I think
live patching would be the coolest. Except . . . it's x86 only for now. The
other stuff I do not really find all that interesting, except some of th
Pretty sure that just means that DT overlays are not in mainline for 4.x.
@Robert, does that mean the next kernel will have overlays in, or . . .?
On Thu, Apr 30, 2015 at 6:39 PM, Rick Mann wrote:
>
> > On Apr 30, 2015, at 18:23 , Robert Nelson
> wrote:
> >
> > On Thu, Apr 30, 2015 at 7:53 PM
> On Apr 30, 2015, at 18:23 , Robert Nelson wrote:
>
> On Thu, Apr 30, 2015 at 7:53 PM, William Hermans wrote:
>> I was just wondering that myself. But more interesting to me. I'm wondering
>> what 4.x is supposed to bring to the table that the other kernels do not
>> have.
>
> Just yet anothe
On Thu, Apr 30, 2015 at 7:53 PM, William Hermans wrote:
> I was just wondering that myself. But more interesting to me. I'm wondering
> what 4.x is supposed to bring to the table that the other kernels do not
> have.
Just yet another kernel away from device tree overlays in mainline.
(aka v3.8.x
I was just wondering that myself. But more interesting to me. I'm wondering
what 4.x is supposed to bring to the table that the other kernels do not
have.
On Thu, Apr 30, 2015 at 5:45 PM, Dan Lipsitt wrote:
> Well, I'm out till Monday so, how about?
>>
>> linux-image-3.14.40-ti-r62
>> linux-imag
>
> Well, I'm out till Monday so, how about?
>
> linux-image-3.14.40-ti-r62
> linux-image-4.1.0-rc1-bone0
>
> both are in the repo, via apt-get..
>
>
>
Thanks. I'll take a look. I'm trying 3.8 for the moment. Is there a feature
matrix somewhere? In terms of what peripherals work on which kern
On Thu, Apr 30, 2015 at 7:32 PM, Dan Lipsitt wrote:
> And another:
Well, I'm out till Monday so, how about?
linux-image-3.14.40-ti-r62
linux-image-4.1.0-rc1-bone0
both are in the repo, via apt-get..
Regards,
--
Robert Nelson
https://rcn-ee.com/
--
For more options, visit http://beagleboard
And another:
[ 569.776621] Unable to handle kernel paging request at virtual address
01010241
[ 569.784293] pgd = c0004000
[ 569.787164] [01010241] *pgd=
[ 569.790986] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[ 569.796572] Modules linked in: ctr ccm usb_f_acm u_serial usb_f_ecm
Similar problem with 3.14.38-ti-r60
Unable to handle kernel paging request at virtual address 0101020d
[ 7574.437128] pgd = c0004000
[ 7574.443300] [0101020d] *pgd=
[ 7574.448344] Internal error: Oops: 817 [#1] PREEMPT SMP ARM
[ 7574.454121] Modules linked in: ctr ccm usb_f_acm u_serial us
If you download the above project you'll find:
README.md - general notes on the OV7670 example
ov7670-cam/pru-ov7670-cape/kicad/ - KiCad schematic and PCB design
ov7670-cam/pru-ov7670-cape/releases/ - PDF schematic and gerbers
I did not put buffers because straight connection works fine for me. Bu
I found one more patch with same problem:
davinci_emac
https://kernel.googlesource.com/pub/scm/linux/kernel/git/horms/ipvs/+/cd2d6d33e2c5be653d10cdc8fcd7dcf0be28de50%5E%21/#F0
Is this one also applied to 4.0.0-bone0?
Sorry for all those questions, I am like a child in the fog.
--
For more optio
Hi Peter.
I replicate this as many times as I want.
I have got can0 interface and SIM908 connected to ttyO2 (GPS) and ttyO4
(GSM).
To achieve this all I need to do is:
Option 1:
run candump can0 in one session of putty
cat /dev/ttyO2 (gives GPS position) on second putty session
Wait a little bit
Great, thank you.
This means it is related to something else.
On Thursday, 30 April 2015 18:25:57 UTC+1, RobertCNelson wrote:
>
> On Thu, Apr 30, 2015 at 12:21 PM, Jan Kinkazu > wrote:
> > Thank you very much for your answer Robert.
> > No I haven't looked anywhere, I am total newbie.
> > All
I observed exactly the same behavior in kernel 3.8.13.
The only difference is, I was able to capture more using debug console.
here is the dump: http://pastebin.com/b73vnbmX
In 4.0.0-bone0 there is only: "unexpected IRQ trap at vector 00"
On Thursday, 30 April 2015 16:00:56 UTC+1, Jan Kinkazu wro
I observed exactly the same behavior in kernel 3.8.13.
The only difference is, I was able to capture more using debug console.
here is the dump: http://pastebin.com/b73vnbmX
In 4.0.0-bone0 there is only: "unexpected IRQ trap at vector 00"
2015-04-30 18:25 GMT+01:00 Robert Nelson :
> On Thu, Apr
Hi Peter.
I replicate this as many times as I want.
I have got can0 interface and SIM908 connected to ttyO2 (GPS) and ttyO4
(GSM).
To achieve this all I need to do is:
Option 1:
run candump can0 in one session of putty
cat /dev/ttyO2 (gives GPS position) on second putty session
Wait a little bit
On Thu, Apr 30, 2015 at 12:21 PM, Jan Kinkazu wrote:
> Thank you very much for your answer Robert.
> No I haven't looked anywhere, I am total newbie.
> All i know is how to compile a kernel using your build_deb.sh and install
> it.
> I have no idea where is a git history.
> I don't know how to che
Thank you very much for your answer Robert.
No I haven't looked anywhere, I am total newbie.
All i know is how to compile a kernel using your build_deb.sh and install
it.
I have no idea where is a git history.
I don't know how to check if this patch has been applied to mainline.
I can't even loca
On 04/30/2015 11:00 AM, Artur Festyn wrote:
> Hi all.
> I am experiencing "unexpected IRQ trap at vector 00" problem on my BBB.
I've had this happen maybe a handful of times in 3 mos., so that's made
it difficult to track down.
How repeatable is this for you?
Regards,
Peter Hurley
--
For more
On Thu, Apr 30, 2015 at 10:00 AM, Artur Festyn wrote:
> Hi all.
> I am experiencing "unexpected IRQ trap at vector 00" problem on my BBB.
> This suppose to be fixed in 3.14 version of kernel as per:
> https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.14.30
>
> cpsw.c
>
> Can anybody tell me
Hi all.
I am experiencing "unexpected IRQ trap at vector 00" problem on my BBB.
This suppose to be fixed in 3.14 version of kernel as per:
https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.14.30
cpsw.c
Can anybody tell me if this patch has been implemented in 4.0.0-bone0?
Kind Regards
Art
On Wed, Apr 29, 2015 at 8:58 AM, Mike wrote:
> Hi Community,
>
> I am student and new to linux and gcc. I have the job to find a toolchain
> for compiling Linux for beaglebone black from Windows x64 host. Cygwin is
> excluded from my options. Therefore I installed the linaro gcc toolchain for
> Wi
Gerald, I've looked into it, and I don't think I could do a good job as
I can't understand TI's documentation. The boot process is described in
Section 26.1 starting at pg 4898 (of SPRUH73K) and summarized in table
26-7 which takes 5 pages; one of the difficulties I have is I don't know
what al
Hi Community,
I am student and new to linux and gcc. I have the job to find a toolchain
for compiling Linux for beaglebone black from Windows x64 host. Cygwin is
excluded from my options. Therefore I installed the linaro gcc toolchain
for Windows (gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_win3
I'm not 100% sure about the 512MB of memory, but I suspect you'd be fine
after the initial setup of the memory controller.. probably best to look at
the memory controller section of the technical reference manual in order to
figure that out. I don't imagine you'd have to deal with any virtual
a
On the front page is the contact information for getting the SRM corrected.
Which page? Which Figure?
I will take a look at this when I can and add it to the next revision as
needed..
Gerald
On Wed, Apr 29, 2015 at 2:38 AM, Gergő Horváth wrote:
> Hi everyone!
>
> While developing an expansio
See inline below.
Gerald
On Wed, Apr 29, 2015 at 7:19 PM, Kenneth Martin
wrote:
> Gerald, I've looked into it, and I don't think I could do a good job as I
> can't understand TI's documentation. The boot process is described in
> Section 26.1 starting at pg 4898 (of SPRUH73K) and summarized in
On Thu, Apr 30, 2015 at 8:48 AM, Tim M wrote:
> Robert, could I connect a keyboard and monitor and see the boot messages on
> the monitor, the same boot messages that would appear on the serial console?
> I'm asking because I could connect a monitor today, but I'd have to order a
> FTDI cable, whi
>
> *But I have a question. My BBB doesn't boot from a microSD, all LEDs come
> on immediately and stay on. How can I connect to it in this state?*
>
In a nutshell . . .uboot has control over the UART until it passes control
over to the OS.
>
> *If I have a serial console connection to the BBB u
Robert, could I connect a keyboard and monitor and see the boot messages on
the monitor, the same boot messages that would appear on the serial
console? I'm asking because I could connect a monitor today, but I'd have
to order a FTDI cable, which would take a few days to arrive.
Thanks,
Tim
--
On Thu, Apr 30, 2015 at 8:11 AM, Tim M wrote:
>> .
>
>
> William, thanks for your help. I will have to buy a FTDI cable before I can
> give this a try.
>
> But I have a question. My BBB doesn't boot from a microSD, all LEDs come on
> immediately and stay on. How can I connect to it in this state?
>
> .
William, thanks for your help. I will have to buy a FTDI cable before I can
give this a try.
But I have a question. My BBB doesn't boot from a microSD, all LEDs come
on immediately and stay on. How can I connect to it in this state?
If I have a serial console connection to the BBB us
I am testing the Beaglebone black C and LCD displayer 4DCAPE-70T that is
pruced by 4D-systems now. If ADconveter that is installed in the beaglebone
black C works, the touch panel that is provided in 4DCAPE-70T works very
slowly and sometimes CPU halts at all.
For example
*root@beaglebone*: ~
Hi Matthijs,
On 04/29/2015 04:12 PM, Matthijs van Duin wrote:
> On Wednesday, 29 April 2015 20:18:51 UTC+2, Andrew Bradford wrote:
>>
>> If you take a BBW and cut the trace coming from U8 pin 5 (the LDO enable
>> line) and then wire U8 pin 5 to the PWR_LED net on page 2 of the
>> schematic, then
35 matches
Mail list logo
