I'm using wheezy. GNU sed version 4.2.1. I see what's happening now.
It looks like the uEnv.txt doesn't have quotes around the kernel version
at all, so there shouldn't be any inner quotes. The only reason my
kernel "update" worked was because the kernel version was the same, so
the sed didn't ne
On Tue, Sep 23, 2014 at 8:50 AM, Robert Nelson wrote:
> On Tue, Sep 23, 2014 at 5:56 AM, Alexander Hayman
> wrote:
>> Hmm, this didn't fix the problem.
>>
>> Preparing to replace linux-image-3.8.13-bone66 1cross (using
>> linux-image-3.8.13-bone66_1cross_armhf.deb) ...
>> Unpacking replacement li
On Tue, Sep 23, 2014 at 5:56 AM, Alexander Hayman
wrote:
> Hmm, this didn't fix the problem.
>
> Preparing to replace linux-image-3.8.13-bone66 1cross (using
> linux-image-3.8.13-bone66_1cross_armhf.deb) ...
> Unpacking replacement linux-image-3.8.13-bone66 ...
> Setting up linux-image-3.8.13-bone
Hmm, this didn't fix the problem.
Preparing to replace linux-image-3.8.13-bone66 1cross (using
linux-image-3.8.13-bone66_1cross_armhf.deb) ...
Unpacking replacement linux-image-3.8.13-bone66 ...
Setting up linux-image-3.8.13-bone66 (1cross) ...
update-initramfs: Generating /boot/initrd.img-3.8.13
I'll double check this on Sunday and report back.
On Friday, September 19, 2014 5:36:08 PM UTC-4, RobertCNelson wrote:
>
> On Fri, Sep 19, 2014 at 10:09 AM, Alex Hayman > wrote:
> > We remerge every week, so I believe we were already using the latest
> > zz-uenv. The error was caused by tryi
On Fri, Sep 19, 2014 at 10:09 AM, Alex Hayman wrote:
> We remerge every week, so I believe we were already using the latest
> zz-uenv. The error was caused by trying to match single quotes in the sed
> command. This can be fixed by replacing the outermost single quotes with
> double quotes.
so t
We remerge every week, so I believe we were already using the latest
zz-uenv. The error was caused by trying to match single quotes in the sed
command. This can be fixed by replacing the outermost single quotes with
double quotes.
Best,
Alex
On Fri, Sep 19, 2014 at 2:47 AM, Alexander Hayman
wro
On Fri, Sep 19, 2014 at 8:06 AM, Charles Steinkuehler
wrote:
> On 9/19/2014 7:19 AM, Robert Nelson wrote:
>>
>> I think we can safely enable this now. Since the flasher is running at
>> boot in a single user environment, usbmount shouldn't mount an
>> external device, so only the base /media/ shou
On 9/19/2014 7:19 AM, Robert Nelson wrote:
>
> I think we can safely enable this now. Since the flasher is running at
> boot in a single user environment, usbmount shouldn't mount an
> external device, so only the base /media/ should be present while
> it's flashing. The whole point of disabling /
On Fri, Sep 19, 2014 at 2:47 AM, Alexander Hayman
wrote:
> Thanks Robert. I've started using the 3.14 kernel (although the less
> bleeding edge bone8 version), and I built a custom dtb to enable both the
> 4Dcape-43t and a secondary non-pin-conflicting uart using your bb-kernel
> repo. It's worke
Thanks Robert. I've started using the 3.14 kernel (although the less
bleeding edge bone8 version), and I built a custom dtb to enable both the
4Dcape-43t and a secondary non-pin-conflicting uart using your bb-kernel
repo. It's worked beautifully. Apologies to Scott for not being able to
follo
On Tue, Sep 2, 2014 at 11:12 AM, Scott Michel wrote:
> Alex:
>
> This conversation seemed to have gotten lost in the myriad of e-mails I get
> per day. Sorry for the delayed reply.
>
> Disable the HDMI interface and enable the 4" LCD, by putting this line into
> /boot/uboot/uEnv.txt:
>
> optargs=c
I don't currently have time to check whether these patches will work. I'm
happy to give you the benefit of the doubt. :)
Alex
On Tuesday, September 2, 2014 12:12:26 PM UTC-4, Scott Michel wrote:
>
> Alex:
>
> This conversation seemed to have gotten lost in the myriad of e-mails I
> get per day
Alex:
This conversation seemed to have gotten lost in the myriad of e-mails I get
per day. Sorry for the delayed reply.
Disable the HDMI interface and enable the 4" LCD, by putting this line into
/boot/uboot/uEnv.txt:
optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
capemgr.enable_p
I checked the difference between the dts's. It looks like the only
difference that matters is the panel-info { bpp } value. BB-BONE has a
bpp of 24. BB-VIEW has a bpp of 32. The display-timings information is
all identical.
Would it then make sense that the image is scaled and the colors a
I am using Robert's bb-kernel git repo to build the kernel. It looks
like we are using the exact same compiler.
Linux version 3.8.13-bone62 (root@debian) (gcc version 4.7.3 20130328
(prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro
GCC 2013.04) )
I noticed that you are passin
Alexander:
Short answer: It works for me. :-)
It turns out that a colleague has an Element-14 4.3" LCD cape here at work.
I just booted up after changing uEnv.txt. Hard to work on the BBB at that
screen resolution, but I don't have the image compression that you
experienced.
I'm not at the most
I can arrange to have one of the 4D Systems 4" LCD's sent to you. If
that would help. I could also do the kernel testing here to help
isolate the offender. I should be able to apply the patches one at a
time and do a quick partial recompile after each patch is applied?
To answer your question a
Robert:
I'll try to get my hands on the Element-14 4" LCD to see if it happens with
that LCD. I have the same company's 7" LCD cape -- should be able to narrow it
down to either the board DTB or a compiler bug.
-scooter
Sent from my iPad
> On Aug 12, 2014, at 5:14 PM, Robert Nelson wrote:
>
Robert:
I don't have the 4" LCD cape, so I really have no way of testing on the
smaller screen. I could break the patch into individual file patches or
more atomic pieces to isolate the offender, if there were someone willing
to test on my behalf.
-scooter
On Tue, Aug 12, 2014 at 5:14 PM, Robe
On Tue, Aug 12, 2014 at 7:06 PM, Scott Michel wrote:
> Alexander:
>
> I apologize for the delayed response -- I've been on travel for a customer
> with more customers keeping me tied up in meetings yesterday and today.
>
> I was going to ask which DTB you were using because your description sounde
On Tue, Aug 12, 2014 at 10:05 AM, Alexander Hayman
wrote:
> I should add that with the patch applied, the modesetting driver works fine,
> but fbdev has the squished image/mangled colors. In my application, I can't
> use modesetting because we need to rotate the screen.
>
> It's been humbling to
22 matches
Mail list logo
