I got it figured out. The SPI dev include dtsi were commented out after my
merge. I guess the default state is SPI devices disabled.
On Sun, Oct 5, 2014 at 1:27 PM, Dallas Clement
wrote:
> Hey Robert, I know this thread is getting long in the tooth. Originally I
> had asked for help on enabli
Hey Robert, I know this thread is getting long in the tooth. Originally I
had asked for help on enabling the SPI devices on the 3.14 kernel. You got
me past that with some patches. However, I just did a merge from the
latest upstream and now my SPI devices are not enabled any more when I boot
th
On Friday, 29 August 2014 10:37:09 UTC-7, RobertCNelson wrote:
>
>
>
> 2nd thought, the uart conflicts..
> so disable:
>
> #include "am335x-bone-basic-proto-cape.dtsi"
> ->
> /* #include "am335x-bone-basic-proto-cape.dtsi" */
>
> Then add spi0:
> #include "am335x-bone-spi0-spidev.dtsi"
>
>
heh whatever you like Jason. Simply using lsblk, and mount should make
things crystal clear.
On Wed, Sep 3, 2014 at 2:57 PM, Jason Lange wrote:
>
>
> On Tuesday, 2 September 2014 16:15:58 UTC-7, William Hermans wrote:
>>
>> Jason,
>>
>> /boot/uboot should have been nothing more than a mount poi
On Tuesday, 2 September 2014 16:15:58 UTC-7, William Hermans wrote:
>
> Jason,
>
> /boot/uboot should have been nothing more than a mount point for
> /dev/mmcblk0p1. Which is the fat16 formatted partition that u-boot.img,
> MLO, and uEnv.txt reside.
>
For a while the fat16 partition was mounte
On Tue, Sep 2, 2014 at 8:58 PM, William Hermans wrote:
> *That's why we've been moving every "critical" file out of that partition.*
>>
>> * For the official lxde image, the fat partition will still be there,*
>> * but NO critical boot files will exist in. (a windows user can add a*
>> * 'uEnv.tx
>
> *That's why we've been moving every "critical" file out of that partition.*
>
> * For the official lxde image, the fat partition will still be there,*
> * but NO critical boot files will exist in. (a windows user can add a*
> * 'uEnv.txt/boot.scr/boot/boot.*
*scr' and it will change the boot..
On Tue, Sep 2, 2014 at 8:23 PM, William Hermans wrote:
> Oh, and nearly forgot for the fifth time heh. What about g_multi file
> "share" ? The one that gets auto mounted on Windows machines. I do not use
> this myself, but I'm sure there are people out there who do use it.
That's why we've been m
On Tue, Sep 2, 2014 at 8:22 PM, William Hermans wrote:
>> /boot/uEnv.txt can be in any partition ( /dev/mmcblkXp1 -> /dev/mmcblkXp7*
>> )
>>
>> 7: is the usual max enabled by default for most normal mmc host
>> controllers in linux.
>>
> Regards,
>
> Right, I get that, but in the case of NFS rootf
Oh, and nearly forgot for the fifth time heh. What about g_multi file
"share" ? The one that gets auto mounted on Windows machines. I do not use
this myself, but I'm sure there are people out there who do use it.
On Tue, Sep 2, 2014 at 6:22 PM, William Hermans wrote:
> */boot/uEnv.txt can be in
>
> */boot/uEnv.txt can be in any partition ( /dev/mmcblkXp1 ->
> /dev/mmcblkXp7* )*
>
> *7: is the usual max enabled by default for most normal mmc host
> controllers in linux.*
>
> *Regards,*
Right, I get that, but in the case of NFS rootfs, how is uboot supposed to
know to look over an NFS shar
On Tue, Sep 2, 2014 at 6:57 PM, William Hermans wrote:
> OK, so I think I got that figured out. Was not familiar with "seek", but
> am now. So what about uEnv.txt ?
>
/boot/uEnv.txt can be in any partition ( /dev/mmcblkXp1 -> /dev/mmcblkXp7* )
7: is the usual max enabled by default for most nor
OK, so I think I got that figured out. Was not familiar with "seek", but am
now. So what about uEnv.txt ?
On Tue, Sep 2, 2014 at 4:52 PM, William Hermans wrote:
> *done ;)*
>>
>> * dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k*
>> * dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=n
>
> *done ;)*
>
> * dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k*
> * dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k*
>
> * only works on omap4+ bootrom's (so the old omap34xx/omap36xx family is
> out)*
>
> * I'm close to rolling out a new testing image that uses this
On Tue, Sep 2, 2014 at 6:45 PM, William Hermans wrote:
>> How would you guys feel about nuking that fat16 "boot" partition. ;)
>
>
> Quite honestly Robert. It's been around since I first got my A5A last year,
> so I'm used to it. But I suppose having one partition formatted as ext2/3/4
> would be
On Tue, Sep 2, 2014 at 5:33 PM, Jason Lange wrote:
> Hello Robert,
>
> I had done just as you've described, but the system I started with had uboot
> and company installed in /boot/uboot rather than /boot and your 'make
> install' in ../dtb-rebuilder.git didn't seem to be touching /boot/uboot. I
>
>
> *How would you guys feel about nuking that fat16 "boot" partition. ;)*
>
Quite honestly Robert. It's been around since I first got my A5A last year,
so I'm used to it. But I suppose having one partition formatted as ext2/3/4
would be more convenient
On Tue, Sep 2, 2014 at 4:40 PM, Robert Nel
On Tue, Sep 2, 2014 at 6:15 PM, William Hermans wrote:
> Jason,
>
> /boot/uboot should have been nothing more than a mount point for
> /dev/mmcblk0p1. Which is the fat16 formatted partition that u-boot.img, MLO,
> and uEnv.txt reside.
How would you guys feel about nuking that fat16 "boot" partiti
Jason,
/boot/uboot should have been nothing more than a mount point for
/dev/mmcblk0p1. Which is the fat16 formatted partition that u-boot.img,
MLO, and uEnv.txt reside.
/boot/uEnv.txt should be nothing more than . ..
*root@arm:~# cat /boot/uEnv.txt*
*uname_r=3.8.13-bone64.1*
*cmdline=quiet init
Hello Robert,
I had done just as you've described, but the system I started with had
uboot and company installed in /boot/uboot rather than /boot and your 'make
install' in ../dtb-rebuilder.git didn't seem to be touching /boot/uboot. I
guessed that that was why I wasn't seeing the changes I was ho
On Fri, Aug 29, 2014 at 12:35 PM, Robert Nelson wrote:
> On Fri, Aug 29, 2014 at 12:20 PM, Jason Lange wrote:
>> Hello Robert,
>>
>> I've just tried to duplicate your instructions here to get both spidev 0 and
>> 1 using your dts from the pastebin link above and I am only getting
>> /dev/spidev1.
On Fri, Aug 29, 2014 at 12:20 PM, Jason Lange wrote:
> Hello Robert,
>
> I've just tried to duplicate your instructions here to get both spidev 0 and
> 1 using your dts from the pastebin link above and I am only getting
> /dev/spidev1.0 and /dev/spidev1.1 -- no spidev0.N or spidev2.N
>
> uname -a:
Hello Robert,
I've just tried to duplicate your instructions here to get both spidev 0
and 1 using your dts from the pastebin link above and I am only getting
/dev/spidev1.0 and /dev/spidev1.1 -- no spidev0.N or spidev2.N
uname -a:
Linux SQR-3 3.14.17-ti-r16 #1 SMP Thu Aug 28 23:18:48 UTC 2014
You're my hero! :) Working like a champ now! Thanks a million.
On Wed, Aug 27, 2014 at 9:42 PM, Robert Nelson
wrote:
> On Wed, Aug 27, 2014 at 9:41 PM, Dallas Clement
> wrote:
> > I just pasted my am335x-boneblack.dts to http://pastebin.com/PwccRatb
>
> Here you go:
>
> http://pastebin.com
On Wed, Aug 27, 2014 at 9:41 PM, Dallas Clement
wrote:
> I just pasted my am335x-boneblack.dts to http://pastebin.com/PwccRatb
Here you go:
http://pastebin.com/rSg1h46h
(just disabled the last line, proto-cape, as it'll inerfear)
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
--
For mo
I just pasted my am335x-boneblack.dts to http://pastebin.com/PwccRatb
On Wed, Aug 27, 2014 at 9:33 PM, Robert Nelson
wrote:
> On Wed, Aug 27, 2014 at 9:23 PM, Robert Nelson
> wrote:
> > On Wed, Aug 27, 2014 at 8:59 PM, Dallas Clement
> > wrote:
> >> Hi Robert, everything builds clean and I
On Wed, Aug 27, 2014 at 9:23 PM, Robert Nelson wrote:
> On Wed, Aug 27, 2014 at 8:59 PM, Dallas Clement
> wrote:
>> Hi Robert, everything builds clean and I can see SPI0 after booting. The
>> devices are spi1.0 and spi1.1. However, I'm not able to see any SPI1
>> devices. Suspecting HDMI confl
On Wed, Aug 27, 2014 at 8:59 PM, Dallas Clement
wrote:
> Hi Robert, everything builds clean and I can see SPI0 after booting. The
> devices are spi1.0 and spi1.1. However, I'm not able to see any SPI1
> devices. Suspecting HDMI conflict, I set the status for the HDMI device to
> "disabled" in
>
Hi Robert, everything builds clean and I can see SPI0 after booting. The
devices are spi1.0 and spi1.1. However, I'm not able to see any SPI1
devices. Suspecting HDMI conflict, I set the status for the HDMI device to
"disabled" in
am335x-base0033.dts. But that didn't seem to help. Anything els
Wow! Thanks for the quick response. Will give it a shot.
On Wed, Aug 27, 2014 at 9:50 AM, Robert Nelson
wrote:
> On Tue, Aug 26, 2014 at 10:56 PM, Robert Nelson
> wrote:
> > On Tue, Aug 26, 2014 at 10:25 PM, Dallas Clement
> > wrote:
> >> Hi Robert, many thanks for this. How dost one actua
On Tue, Aug 26, 2014 at 10:56 PM, Robert Nelson wrote:
> On Tue, Aug 26, 2014 at 10:25 PM, Dallas Clement
> wrote:
>> Hi Robert, many thanks for this. How dost one actually enable the spi
>> devices in 3.14? I'm used to working with the overlays and capemgr, i.e.
>> echoing to capemgr slots etc
On Tue, Aug 26, 2014 at 10:25 PM, Dallas Clement
wrote:
> Hi Robert, many thanks for this. How dost one actually enable the spi
> devices in 3.14? I'm used to working with the overlays and capemgr, i.e.
> echoing to capemgr slots etc.
Well it's still in it's infancy.
Here's what works today:
h
Hi Robert, many thanks for this. How dost one actually enable the spi
devices in 3.14? I'm used to working with the overlays and capemgr, i.e.
echoing to capemgr slots etc.
On Tue, Aug 26, 2014 at 8:39 PM, Robert Nelson
wrote:
> On Tue, Aug 26, 2014 at 8:28 PM, Robert Nelson
> wrote:
> > On
On Tue, Aug 26, 2014 at 8:28 PM, Robert Nelson wrote:
> On Tue, Aug 26, 2014 at 8:05 PM, Dallas Clement
> wrote:
>> Hi All,
>>
>> I am trying to enable both SPI devices in the 3.14 kernel for a beaglebone
>> black. I understand that the capemgr support is no longer there. I need
>> some tips on
On Tue, Aug 26, 2014 at 8:05 PM, Dallas Clement
wrote:
> Hi All,
>
> I am trying to enable both SPI devices in the 3.14 kernel for a beaglebone
> black. I understand that the capemgr support is no longer there. I need
> some tips on how to enable these devices in the kernel. I don't care if it
35 matches
Mail list logo
