**** BEGIN LOGGING AT Mon Mar 28 02:59:58 2016 Mar 28 07:31:45 spidev2.0 not working. Returns error message as "SPI: SPI_IOC_MESSAGE Failed: Invalid argument" Mar 28 07:32:11 any idea for the occurence of this type of perror? Mar 28 07:32:39 using kernel:armv7l Linux 4.1.18-ti-r53 Mar 28 07:32:47 debian Mar 28 10:45:43 Can you install generic ARM linux distros on the BeagleBone Black or do you need custom ones like the raspberry pi? Mar 28 11:27:52 Qwertie: yes, many have native images Mar 28 11:28:36 or it's easy to take a generic armv7 image and adapt it Mar 28 13:35:32 Hi, I'm looking to talk to my beaglebone over an azure virtual machine, (external network). Any good tutorials to get up and running with this? Mar 28 13:54:52 Heelo, can someone help me map the virtual addresses one can get out of the System.map file to the address space of the UBOOT console? Mar 28 14:26:44 raffo: u-boot console, you mean the serial port via uart? Mar 28 14:26:56 if so, look in the TRM for am335x Mar 28 14:27:29 yes, the serial console. Mar 28 14:28:10 I'm testing on an OMAP5432. Mar 28 14:28:31 raffo: OMAP5432? which beagleboard is that on? Mar 28 14:29:31 I'm testing on a couple of boards. My interest is in the Beagleboard x15. Mar 28 14:30:39 raffo: does the technical reference manual for OMAP5432 not state what the memory map is and the location of the UARTs? Mar 28 14:31:23 the kernel is not showing any output on boot, so I'd like to dump the kernel log that is kept in memory before the serial console is activated. Mar 28 14:32:04 raffo: do you have earlyprintk enabled in linux? Mar 28 14:32:19 raffo: do you have the serial port drivers compiled into linux? Mar 28 14:32:27 raffo: do you have your device tree setup right? Mar 28 14:33:04 Yes, all "debug" and "earlyprintk" are enabled. The same image loads on different board. We're testing a new board. Mar 28 14:33:37 the kernel outputs debug info on the functional board. Mar 28 14:35:42 From google search, I learned that there is a log buffer where early messages are stored. I got the address from the kernel's System.map file, what I am trying to figure out is how to translate this into an address I can pass to the md command in u-boot. Mar 28 14:41:28 Hi, could someone pastebin the output of /lib/firmware on her/his Jessie distrib bbb please ? Mar 28 18:18:07 dirkk_: Sure can, one moment. Mar 28 18:22:46 dirkk_: http://pastebin.com/d7Bq3G8V Mar 28 19:12:19 How in the world do people avoid naming collisions when packaging files on Linux? With so many packages out there I'm amazed that it doesn't happen all the time. Mar 28 21:09:49 MathOnNapkins: because distributions have maintainers :P Mar 28 21:10:56 also, APT doesn't see a package name collision as a problem, it just lists them as two versions of the same package Mar 28 21:11:35 but package naming for the debian repositories is centralized, you can't just upload any random stuff there Mar 28 21:12:33 ping rcn-ee Mar 28 22:00:23 Are there notes on where to retrieve the source code of the kernel used in the Beagleboard x15 images you can download at http://elinux.org/BeagleBoardUbuntu? Mar 28 22:23:13 I suspect the same one as the debian kernel? Mar 28 22:24:23 what's the linux-image package name and version? Mar 28 22:26:45 yeah, definitely same one as the debian packages Mar 28 22:29:22 you can find the patched kernel trees for rcn-ee's releases here: https://github.com/RobertCNelson/linux-stable-rcn-ee/releases Mar 28 22:30:31 instead of searching through the list you can also just use an url like this (example for the 2016-03-11 default kernel): https://github.com/RobertCNelson/linux-stable-rcn-ee/tree/4.1.18-ti-r52 Mar 28 22:32:55 these trees are actually generated by scripts which apply a series of patches to some mainline kernel. https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/4.1.18-ti-r52 Mar 28 22:34:19 (that repo is for the -ti series, e.g. the "ti-linux-4.1.y" branch corresponds to the latest 4.1-ti kernel) **** ENDING LOGGING AT Tue Mar 29 02:59:58 2016