**** BEGIN LOGGING AT Tue Jan 10 03:00:02 2017 Jan 10 03:39:38 Hi Jan 10 03:41:51 is anyone here? Jan 10 03:42:17 well, anyway.. My name is Camilo, and I'm from Chile Jan 10 04:57:29 I wonder what would actually be the most efficient way to mirror a BBB back to my laptop's display. VNC? Jan 10 04:57:36 * ericxdu will have to google it Jan 10 05:55:44 ericxdu: efficient in what sense? Jan 10 05:57:48 and do you actually need to mirror (i.e. grab a copy of data being displayed via LCDC), or just have an X session running on the BBB, or just one or more X applications? Jan 10 05:59:01 (for the last option using ssh -X would definitely be most efficient in terms of your time, since it's a proven solution that works out of the box) Jan 10 07:47:41 zmatt: I do want a full desktop session, with minimal latency Jan 10 08:40:31 zmatt: seems goes to suspend but doesn't wake up :/ I'll try with the 4.9 robert's kernel Jan 10 09:10:02 eballetbo: how did you try waking it up? wakeup sources may need to be configured, I'm not sure Jan 10 09:10:59 you can probably also enable debug messages to see if it progressed through suspend correctly Jan 10 09:12:16 zmatt: guess that pressing a key in serial port should wake up Jan 10 09:13:06 it should. it was also enabled as wakeup source by default last time I tried suspend/resume, but that was quite a while ago, probably on a 4.1-ti kernel Jan 10 09:21:58 ericxdu: xvnc, x2go, xrdp, lots of options Jan 10 11:00:38 hello guys, i have some devices in beaglebone to which only root has access, when i change permissions manually to 666 or 777 on the device, it returns back after reset.. how can i preserve permissions after reset? Jan 10 11:06:41 help Jan 10 11:08:10 nardev: depends. if its about serial ports or such, just add the user to the group dialout. for more detailed modifications, add a udev rule. Jan 10 11:24:39 LetoThe2nd, only dialout group is important? Jan 10 11:24:52 i want to be able to access all ports as root is able.. Jan 10 11:25:07 i have some analog some gpio and some i2c pins connected Jan 10 11:50:47 nardev: then look up udev rules. dialout is only relevant for uarts. Jan 10 12:03:42 Hi, would like to find out how to access 2 i2c bus Jan 10 12:13:57 jkridner: we could really use a notice on the chat webpage explaining that people should have patience after asking a question Jan 10 12:24:18 nardev: here are some example udev rules I use on our beaglebones... perhaps they're of use for inspiration: http://pastebin.com/1ZRMbsan Jan 10 13:21:18 hiii Jan 10 14:19:45 zmatt: thank you. Definitely lots of options. :-D Jan 10 15:54:33 if you dd MLO and u-boot.img to an SD card, is it necessary to have a FAT partition as /boot as well? Jan 10 15:57:56 zmatt, last time you tryied s2r, which version did you use? sorry, guess I lost the backlog Jan 10 16:32:07 rah: sorry, but this is ridiculous... instead of asking here you could have obtained your answer with trivial effort by inspecting any standard beaglebone image (which have not used a FAT partition since ages) and moreover I already explained this two days ago Jan 10 16:33:26 zmatt: I'm sorry but that's ridiculous... if you had explained it, why would I come here and ask? Jan 10 16:33:39 03:00:42 < zmatt> when booting from uSD or eMMC either "raw mmc" or a FAT partition can be used for storing the MLO Jan 10 16:33:42 03:01:00 < zmatt> if both are present, raw mmc boot is preferred and the FAT partition is ignored Jan 10 16:33:45 03:01:40 < zmatt> standard beaglebone images have used raw mmc boot instead of a FAT boot partition for a long time now Jan 10 16:33:48 03:11:46 < rah> I see Jan 10 16:33:55 I explained, and you acknowledged that you received the explanation Jan 10 16:33:59 zmatt: also, I don't know what images you're referring to as "standard"; I can't find any images for beaglebones on debian.org Jan 10 16:34:43 http://lmgtfy.com/?q=beaglebone+image Jan 10 16:34:45 http://lmgtfy.com/?q=beaglebone+debian Jan 10 16:36:20 zmatt: well, actually your comments have not answered my question Jan 10 16:36:29 yes they di Jan 10 16:36:31 *do Jan 10 16:36:46 zmatt: I asked if a FAT partition was necessary Jan 10 16:37:20 and how is that question not answered by no fat partition being present on the images used by default on beaglebones? Jan 10 16:37:48 "raw mmc or a FAT partition can be used." I see it right there. Jan 10 16:37:56 zmatt: you didn't say there was no fat partition present Jan 10 16:37:58 yeah, "either... or..." Jan 10 16:38:11 "used raw mmc boot instead of a FAT boot partition" Jan 10 16:39:35 zmatt: you didn't say used for what though Jan 10 16:39:53 while not completely excluded in theory, it makes no sense that a FAT partition would be required if it's not used. more importantly, you could still have 1. inspected a standard image and observe its total absence 2. TRIED IT YOURSELF :D Jan 10 16:40:51 you keep saying "standard" Jan 10 16:41:08 the problem is that what you see as "standard" images, I see as "non-standard" images Jan 10 16:41:16 and it's the "non-standard" that keeps me away from them Jan 10 16:41:21 yes, as in preinstalled on new beaglebones, found on the beaglebone website, top google hit for any plausible search Jan 10 16:41:32 that's your problem and not a reason to waste our time Jan 10 16:41:35 but not from Debian Jan 10 16:41:54 err Jan 10 16:41:57 can we all just get along? rah, you now have your answer Jan 10 16:42:02 you don't need a FAT partition Jan 10 16:42:05 you're under no obligation to answer questions Jan 10 16:42:28 I'm not wasting anyone's time by asking a question Jan 10 16:43:23 if you think a question's answer is too obvious and that the asker should find out for themselves, then you can simply ignore the question and carry on with your day Jan 10 16:43:27 I do that all the time :-) Jan 10 16:44:10 but thanks for engaging in this instance, now I understand Jan 10 16:45:36 please if you're wondering about how a system running on the bbb works, install the default image and study how it works first before trying to concoct your own image from scratch Jan 10 16:46:08 I'll bear that in mind Jan 10 16:46:24 however Jan 10 16:46:52 I'm looking at beagleboard.org Jan 10 16:47:03 whatever issue you have with the default images, it's not going to taint your bbb beyond redemption, I promise :P Jan 10 16:47:12 there isn't much information about who is putting together these images Jan 10 16:47:17 I don't know where they're coming from Jan 10 16:47:33 how much do you know about the factory workers who made your beaglebone? Jan 10 16:47:48 the people working at TI who designed the SoC? Jan 10 16:47:56 The images on beagleboard.org are as "standard" as you're going to get rah Jan 10 16:48:07 and there are serious problems in the legalities of the beagleboard's design, which I've had no success trying to deal with Jan 10 16:48:53 and going through that process has drastically reduced by confidence whoever the people are behind beagleboards Jan 10 16:49:18 s/by confidence/my confidence/ Jan 10 16:49:25 urgh Jan 10 16:49:33 s/confidence whoever/confidence in whoever/ Jan 10 16:50:28 I have no idea what you expect anyone to do with such a vague statement Jan 10 16:50:34 ^ Jan 10 16:51:06 the people running it are not perfect, neither is the default image Jan 10 16:51:09 neither is debian Jan 10 16:51:13 nor linux Jan 10 16:51:31 but I have never seen reason to doubt their intentions Jan 10 16:53:00 I expect you to think 'hmm.. perhaps this guy's lack of confidence in those setting the "standard" for beagleboard images should not be dismissed' and then allow that thought to inform your future interactions with beagleboard.org, beagleboard.org foundation, beagleboard.org image makers, beagleboard manufacturers, or whoever else you come in to contact with Jan 10 16:53:33 lol Jan 10 16:53:41 I have no reason to doubt their intentions Jan 10 16:56:43 you're some random guy coming in here making a vague accusation of some sort without even really saying what your problem is let alone substantiate it, and you expect people to take you serious? Jan 10 16:57:00 I suggest you adjust your expectations Jan 10 16:57:06 I've been in here before asking about it Jan 10 16:57:34 I've been in this channel for a while :-) Jan 10 16:57:55 bad choice of words, I meant more like "came into my view". I do recall having seen your nick before but I don't have any specific memories or feelings linked to it Jan 10 16:58:32 the remainder of what I said still stands Jan 10 16:58:38 the problem is that the design files for, at least the beaglebone green and beaglebone black, are not licensed Jan 10 16:58:47 there is no declaration of what license they are under Jan 10 16:59:27 nor is there any information published about the license of the design files Jan 10 17:00:46 http://elinux.org/Beagleboard:BeagleBoneBlack#Terms_of_Use Jan 10 17:01:18 zmatt: this section of the website contains conflicting information Jan 10 17:02:11 zmatt: not to mention that it's a hodgepodge of badly written, mashed together paragraphs Jan 10 17:02:11 it isn't written terribly well but I see no conflict, and certainly no ambiguity about the license Jan 10 17:02:24 "There are no licences involved in the usage of the BeagleBone Black design materials Jan 10 17:02:29 "This work is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License" Jan 10 17:02:53 of course, it isn't really clear what the "this work" in the second sentence is referring to Jan 10 17:02:56 yes that's a poor choice of words, although it is clear what is meant Jan 10 17:02:59 is it the design files or the wiki? Jan 10 17:03:01 we can only guess Jan 10 17:03:09 it isn't clear what is meant Jan 10 17:03:17 that's the problem Jan 10 17:04:07 in my opinion it is perfectly clear even if not written well. Jan 10 17:08:12 note that the green is designed by seeed studio, not by beagleboard.org Jan 10 17:10:33 I also don't really see an explanation of what your issue with sloppy writing w.r.t. licensing of the hardware design has to do with the default firmware images Jan 10 17:11:07 I take it back, the issue is the beaglebone.org designs; the beaglebone green design files have a license declaration in them Jan 10 17:11:30 (they use the same firmware image btw) Jan 10 17:12:22 well, it's like this.. in my mind, the people who run beagleboard.org, who release design files without license declarations in them, and who wrote that "terms of use" section, are dickheads :-) Jan 10 17:12:51 well, thank you for giving that bit of insight into your mind Jan 10 17:14:04 I'm not really interested in anyone who puts such a massive amount of effort into producing so-called "Debian" images but not doing so in the Debian way, or feeding their changes back into Debian Jan 10 17:14:36 the images for the beaglebone are not standard debian installs, aren't intended to be, and never will Jan 10 17:14:45 they're designed for the beaglebones Jan 10 17:15:05 the beagleboard.org people seem to be a closed group who just take Debain as a base for $their_thing instead of making it so that Debian proper can serve the same function Jan 10 17:15:24 right Jan 10 17:15:29 they're not intended to be Jan 10 17:15:41 and it's that lack of intention that repels me Jan 10 17:15:48 they contain a ton of custom software that makes no sense outside the beaglebone Jan 10 17:15:55 a beaglebone is not a standard desktop computer Jan 10 17:16:29 kernel patches do get upstreamed whenever it makes sense Jan 10 17:17:21 I find the assertion that the "custom" software for the beagleboard is only of value to beagleboard users/developers Jan 10 17:17:35 regardless, even if it is, there's no reason it can't be packaged for Debian proper Jan 10 17:17:55 argh Jan 10 17:17:59 parts of it probably are Jan 10 17:18:05 I find the assertion that the "custom" software for the beagleboard is only of value to beagleboard users/developers, to be highly suspicious Jan 10 17:18:06 I really don't understand what you're even getting at Jan 10 17:18:31 I'm not getting at anything Jan 10 17:18:37 rah: I recommend avoiding BeagleBone. With all the butt hurt you experience it seems clear it's not a good fit for your needs. Complaining about it will not make it fit your needs. Jan 10 17:18:46 the main custom stuff is related to the beaglebone itself, the hardware Jan 10 17:18:54 Ragnorok: thanks, I'm way ahead of you there though :-) Jan 10 17:18:55 that's what the kernel is tweaked for also Jan 10 17:19:03 rah: Then why are you still complaining? Jan 10 17:19:04 other than that, the base image is standard debian Jan 10 17:19:05 Ragnorok: but I made the mistake of buying one so I'm here for now :-) Jan 10 17:19:08 which also means standard debian works fine Jan 10 17:19:15 perhaps apart from the kernel Jan 10 17:19:24 (I don't know, I haven't tried) Jan 10 17:19:45 rah: It's not a mistake. We have production systems deployed using them. They are quite capable. From this chair the issue is not the BeagleBone. Jan 10 17:19:53 that. Jan 10 17:22:31 .... and if it was a mistake to buy it ... -> http://www.ebay.com/ might help ;) Jan 10 17:22:46 surely more productive than ranting and venting Jan 10 17:28:36 rah: I just checked, what's running on our beaglebones consists just of debian packages and our own custom stuff Jan 10 17:30:48 maybe there's no ready-to-use vanilla debian image (I haven't looked since I don't care), but providing those is debian's job, not beagleboard.org's Jan 10 17:31:19 they provide debian-based images configured in a way they think is useful for beaglebone users Jan 10 17:32:49 kay, back to doing something useful Jan 10 17:33:16 wut? Jan 10 17:34:55 hmm, is the surprise about me doing something useful? it does happen sometimes :) Jan 10 17:35:44 The surprise is that you'd be doing something other than helping peeps here. I can't remember last time you weren't at it. Jan 10 17:36:25 heh Jan 10 17:37:18 yes I also have an actual job ;) and need to do shopping now and then Jan 10 17:37:50 and I'm reverse-engineering the undocumented instruction set of a DSP we use and work on a code generator for it Jan 10 17:37:58 and occasionally sleep Jan 10 17:38:29 Undoc'd stuff. Always fun. Jan 10 17:41:45 this thing is fascinating... on one hand it has some really nice stuff, e.g. it can calculate a dot product with 32-bit operands at a rate of 4 terms/cycle, and all pointer registers have hardware support for circular buffers Jan 10 17:42:33 at the same time the only usable rounding mode is to -infty... round to nearest and round toward zero are broken for negative numbers Jan 10 17:43:29 fucking up round-to-nearest is quite an accomplishment I think Jan 10 17:48:28 Maybe they didn't think anyone would try something so crazy :3 Jan 10 17:49:25 I actually think they somehow managed to accidently use a piece of logic designed for sign-magnitude representation Jan 10 17:49:39 (the dsp uses two's complement) Jan 10 17:49:57 perhaps they should have supervised that intern a bit better :P Jan 10 17:50:50 it doesn't matter hugely in practice, but it was still a wtf Jan 10 17:53:29 heh Jan 10 17:53:43 Interns. Sheesh. Jan 10 17:54:02 well that's my best guess Jan 10 17:54:15 * Ragnorok is rolling with it Jan 10 17:57:11 how else do you get a rounding mode that effectively does: int round( int msw, uint lsw ) { return msw + (bit31(lsw) ^ bit31(msw)); } Jan 10 17:57:50 for negative numbers it's neither idempotent nor monotone Jan 10 17:58:10 it's also more complicated than the correct msw + bit31(lsw) Jan 10 17:58:47 zmatt, Jan 10 17:58:49 thnx Jan 10 17:59:03 you're welcome Jan 10 18:24:05 aargh, none of the kernels I tried has s2r working :( Jan 10 20:33:06 Ragnorok: my concern is not that the machine won't work; if that was my only concern, I would probably still be using Windows Jan 10 20:33:17 Ragnorok: do you use Windows by any chance? :-) Jan 10 20:33:33 eballetbo: ok that sounds weird, I absolutely did have it working (without effort) Jan 10 20:33:33 I do, b/c work says to. Jan 10 20:33:50 eballetbo: I don't remember when exactly, a while ago... Jan 10 20:36:32 zmatt: again, I question beagleboard.org if they think that stock debian working as perfectly as their current debian-ish images, would not be useful to beagleboard users Jan 10 20:37:10 Ragnorok: you have my condolences Jan 10 20:37:19 rah: then you're really misguided Jan 10 20:37:31 Ragnorok: can you not find a company that will allow you to use a free operating system? Jan 10 20:37:43 zmatt: I disagree Jan 10 20:37:56 no doubt Jan 10 20:40:25 rah: Opinions are like assholes - everybody is one. Jan 10 20:40:56 *has Jan 10 20:41:18 I typed what I meant. Jan 10 20:41:58 Ragnorok: do you concern yourself with the freedom of the operating system you use? Jan 10 20:42:04 eballetbo: I'll give it a try in a moment Jan 10 20:43:34 rah: why are you still here wasting your and other people's time? I thought you had already concluded the beaglebone was not a good choice for you, and various people agreed in unison Jan 10 20:43:52 rah: I accept the opinions of others are not likely to align with my opinions. I reject another trying to ram their opinions down my throat. Jan 10 20:44:04 sell it on ebay, find a board that makes you happier Jan 10 20:44:51 Ragnorok: I'm just curious Jan 10 20:45:11 Ragnorok: I'm not going to cry about it if you don't concern yourself :-) Jan 10 20:45:26 Ragnorok: *do* you concern yourself? Jan 10 20:46:39 zmatt: well, unfortunately the damage is done now and if I sold it on ebay I'd make a loss Jan 10 20:46:47 I don't use an operating system as a basis for career decisions, no. I've worked with about everything except apple. Jan 10 20:47:09 rah: unless you value your time as worth $0, you're increasing your loss right now Jan 10 20:47:14 Ragnorok: do you have Windows on your personal computers? Jan 10 20:47:35 zmatt: this activity has value to me Jan 10 20:47:50 you like being annoying? Jan 10 20:48:10 Some of them. Some of them have Linux. I use the OS that fits the need. Jan 10 20:48:54 zmatt: it's not often that I converse on IRC with people outside the free software movement Jan 10 20:48:58 Ragnorok: I see Jan 10 20:50:04 rah: because they kick you out or /ignore you maybe? Jan 10 20:50:10 zmatt: it has value to me in just reminding myself that there actually exist people who use computers and don't concern themselves with issues of freedom :-) Jan 10 20:51:01 zmatt: no, I just run in circles where concern for freedom is a given Jan 10 20:51:15 Nice Jan 10 20:51:32 I must admit that /ignore is getting rapidly more tempting, even though it would be the second time in a decade or so that I'd use it on a human rather than a bot Jan 10 20:51:45 blimey Jan 10 20:51:50 I must be doing something right :-) Jan 10 20:52:04 to get someone so worked up, they must really care about what I'm saying ;-) Jan 10 20:52:11 I have a i2c device hooked up to my beagle board black but whenever i do i2cdetect it wont find it Jan 10 20:52:25 Is this a question board? Jan 10 20:52:41 Geo_: normally, yes Jan 10 20:52:54 Geo_: What does ls /dev/i2c* show? Jan 10 20:53:41 rah: have you considered the possibility that you simply are being *that* obnoxious? Jan 10 21:05:35 merde Jan 10 21:05:45 eballetbo: installing kernel... Jan 10 21:05:47 I was waiting for vagrantc :-/ Jan 10 21:07:53 Spidler: btw, I came across this blog post, I thought you might find it interesting also :) -> http://www.bunniestudios.com/blog/?page_id=1022 Jan 10 21:08:15 froggyman! Jan 10 21:08:29 Does anyone have a good example on how to use the shared memory on PRU ? (between host and PRU0 for instance) Jan 10 21:09:36 I used a struct to define data fields. Both the PRU & Linux use that struct. It has the advantage of simplicity. Jan 10 21:09:48 davidcm: what constitutes a "good example" for using a piece of memory? Jan 10 21:10:31 zmatt: Ok, good point. Let me raphrase it. First of all, how to initialize both ends to point to the same space Jan 10 21:11:15 i found this: https://github.com/texane/pru_sdk/tree/master/example/pruss_c Jan 10 21:11:51 which is using the 12KB shared ram apparently Jan 10 21:13:10 never seen that tree before, it seems to be doing weird things Jan 10 21:13:13 I was looking for some C code example to access the ram from both ends for instance Jan 10 21:13:33 the prussdrv library has a function for mapping the shared ram on the linux side Jan 10 21:14:23 It does. It's not hard to use and has many examples. Jan 10 21:15:33 prussdrv_map_prumem(PRUSS0_SHARED_DATARAM, &sharedmem) Jan 10 21:15:36 or so Jan 10 21:16:32 ok let me check that Jan 10 21:18:08 that looks pretty easy actually. What about on the PRU side ? Jan 10 21:18:11 on the pru side it's at a fixed address, 0x10000 Jan 10 21:18:36 you could also configure constants register c28 to point to it (or some location in it) for convenience Jan 10 21:19:27 ok, got it Jan 10 21:20:55 for reference, http://pastebin.com/gT2RsL4Q Jan 10 21:24:42 note that PRU reads that go out to the L3 (address >= 0x80000) are very slow in comparison to local memories, and (for some applications even worse) have variable timing; same goes for writes after you filled up the fifo to the L3 interconnect Jan 10 21:25:10 the 12 KB shared ram is still local of course, but I just want to ensure you know about this to avoid unpleasant surprises later Jan 10 21:25:25 yeah makes sense Jan 10 21:25:29 good stuff thanks Jan 10 21:25:56 iirc local is 1+(num words) cycles (or maybe 2+, don't immediately remember) Jan 10 21:27:07 if you hit the L3, iirc it was... oh wait, this is handy: http://processors.wiki.ti.com/index.php/AM335x_PRU_Read_Latencies Jan 10 21:28:11 it is :) Jan 10 21:29:20 it would have been nicer if the compared a few transfer sizes Jan 10 21:29:25 I'm assuming these are all single-word Jan 10 21:29:51 except maybe table 3, it's not clear what code they used there Jan 10 21:38:29 eballetbo: suspend and resume worked without problem for me Jan 10 21:39:22 on latest 4.4-ti (4.4.40-ti-r80) Jan 10 21:43:29 http://pastebin.com/fGJUH52C Jan 10 21:47:33 4.9.0-bone3 does not seem to support suspend Jan 10 21:48:01 (write error: Invalid argument) Jan 10 21:53:19 (nor I didn't expect it to work really, but I already had that kernel installed so might as well try) Jan 10 21:56:06 no luck on 4.9.0-ti-r10, so the 4.9-ti series doesn't support suspend yet for some reason Jan 10 21:56:39 I would expect that to work sooner or later Jan 10 22:07:01 eballetbo: so for now you'll need to use 4.4-ti if you need suspend Jan 10 22:08:13 zmatt: I'm not normally this obnoxious but you were defending beagleboard.org so I took the opportunity to poke you in the eye :-) Jan 10 22:08:18 I'm sorry Jan 10 22:08:20 please forgive me Jan 10 22:09:17 rah: ? Jan 10 22:09:26 zmatt: the console images are pretty close to vanilla. Jan 10 22:09:41 I know, that's what I said Jan 10 22:09:47 oh, I missed it. Jan 10 22:10:44 * jkridner just saw rah's comment about defending beagleboard.org and isn't keen to read a lot of scrollback. Jan 10 22:10:56 it's not worth reading Jan 10 22:11:04 lol Jan 10 22:11:49 jkridner: http://codepad.org/g6MRf0lQ Jan 10 22:12:22 I've been in contact with Gerald Coley about it Jan 10 22:12:30 his response was disturbing Jan 10 22:12:54 BeagleBone Green design files are published. Jan 10 22:13:11 your response right there is disturbing Jan 10 22:13:21 ah, you are talking about the license. Jan 10 22:13:42 well, for BeagleBone Black, the materials themselves are released under Creative Commons.... Jan 10 22:13:57 that's great Jan 10 22:14:02 except you nobody knows that Jan 10 22:14:02 and that has no bearing on their right to be manufactured.... Jan 10 22:14:11 So we are running out of colors. We have green black white and now blue. What's left yellow and purple? Jan 10 22:14:12 s/you nobody/ Jan 10 22:14:29 jkridner: actually it does Jan 10 22:14:40 jkridner: you can't copy the .pdf without a license; it's a copyrighted work Jan 10 22:14:57 Teal! I'm waiting anxiously for a BBT. Jan 10 22:15:10 yes, but the license is public. Jan 10 22:15:26 the BBE is also blue Jan 10 22:15:30 jkridner: what do you mean "the license is public"? there are no license notices in the design files Jan 10 22:15:36 I've looked Jan 10 22:15:39 and the BBB industrial is red Jan 10 22:15:49 Gerald Coley admits there's no notice Jan 10 22:15:49 Mine's not. Jan 10 22:15:54 I thought it was? Jan 10 22:16:17 FYI, SeeedStudio BeagleBone Green is a product of Seeed, not BeagleBoard.org, but we have requirements that they release the materials under an open license. Jan 10 22:16:25 zmatt: Could be the source. Mine are all oddly black. Jan 10 22:16:42 jkridner: right, and on the front page of their schematic PDF is a declaration that the work is licensed under a CC license Jan 10 22:16:59 jkridner: there is no such declaration on any beagleboard.org design files that I could find Jan 10 22:17:10 jkridner: Seeed are doing it right Jan 10 22:17:18 rah: I'll see what I can do to add the license to https://github.com/beagleboard/beaglebone-black Jan 10 22:17:37 hi jkridner Jan 10 22:17:55 jkridner: why not add it to the design files themselves, like Seeed? Jan 10 22:18:14 https://github.com/beagleboard/beaglebone-black-wireless is an example of what I published. Jan 10 22:20:00 jkridner: great, there's at least a LICENSE file in the repository, if not a notice in the files themselves, that's a step up Jan 10 22:20:24 what about https://github.com/beagleboard/beagleboard-xm https://github.com/beagleboard/beagleboard-x15 https://github.com/beagleboard/BeagleBoard https://github.com/beagleboard/BeagleBone etc.? Jan 10 22:20:32 jkridner: btw, could you check these bits of scrollback: http://pastebin.com/mAJ07qtq Jan 10 22:21:45 rah: easier to fix in newer items, rather than backtracking complex ownership issues, but, like I said, I'll see what I can do to make sure it gets clearer in the repo itself. Jan 10 22:22:00 jkridner: also http://elinux.org/Beagleboard:BeagleBoneBlack#Terms_of_Use does more harm than good Jan 10 22:22:05 https://beagleboard.org/hardware/design was the original location for publication. Jan 10 22:22:42 jkridner: also the smart-questions guide link doesn't work with https: and should be changed to http: Jan 10 22:22:43 the original release of the original design files was https://groups.google.com/forum/#!msg/beagleboard/8LCOQBQ42kQ/_B9VJ8kbPu4J Jan 10 22:22:47 and irclogs are broken Jan 10 22:22:50 zmatt: thought I just fixed that. Jan 10 22:22:51 I created an elinux.org account to fix that wiki page but unfortunately it seems that some users are more free than others to edit that page Jan 10 22:25:27 zmatt: ah... it was the survival guide link I fixed. Jan 10 22:26:12 jkridner: you seem more reasonable than Gerald Jan 10 22:26:29 my view of beagleboard.org has become less hate-filled :-) Jan 10 22:26:34 no comment. :-) Jan 10 22:26:44 that was probably too much comment. Jan 10 22:27:17 FYI, Gerald isn't an official board member anymore, but he's still a very key member in the community. He did all the hard design work on the first 5 or 6 boards. Jan 10 22:28:01 zmatt: removed the 'https', so that link works now. Jan 10 22:28:09 I'll work on the logs later... need to get to a workshop now. Jan 10 22:28:20 jkridner: the survival guide contains good points, but it's not ideal for our purposes, with silly stuff like the youtube video, and the prioritization is off; i.e. his summary puts "6. Wait" at the bottom of the list, while getting people to have patience is probably the most important point needed here Jan 10 22:29:15 it really needs to be much more in-your-face that saying "hi" or "is anyone here?" and then leave again 5 minutes later is not a productive way to use this channel Jan 10 22:32:09 jkridner: did the blue come out yet?! Jan 10 22:32:29 zmatt: +5 Jan 10 22:32:58 veremit: no, 10 minutes isn't enough either Jan 10 22:32:59 ;) Jan 10 22:33:08 zmatt: :P Jan 10 22:33:15 http://www.catb.org/esr/faqs/smart-questions.html Jan 10 22:33:18 ;) Jan 10 22:35:34 veremit: the A2 design is published on my private github and we have a number of boards, but we haven't entered production yet. Jan 10 22:36:41 jkridner: sounds cool Jan 10 22:37:13 jkridner: any eta?! Jan 10 22:37:55 Pay attention at Embedded World. Jan 10 22:38:25 jkridner: where's that?! :P Jan 10 22:38:38 Germany Jan 10 22:39:00 oh cool - I'm off to FOSDEM next month Jan 10 22:39:04 its free :) Jan 10 22:39:23 * jkridner would love to go to FOSDEM some day. Jan 10 22:40:06 * Ragnorok would love to go to a con some day Jan 10 22:41:04 jkridner: lookin forward to it :D Jan 10 22:50:07 zmatt: many thanks, is this kernel right ? (https://git.ti.com/ti-linux-kernel/ti-linux-kernel/commits/ti-linux-4.4.y) Jan 10 22:52:40 uhh Jan 10 22:52:43 apt-get install ? Jan 10 22:53:47 it's based on that tree, but with patches and config specific for the beaglebone family and beagleboard-x15, built and packaged by rcn Jan 10 22:54:55 you can find his build repo for that tree here: https://github.com/RobertCNelson/ti-linux-kernel-dev/tree/ti-linux-4.4.y Jan 10 22:55:25 oh, :(, no git for this kernel then, ok i'm gonna try this Jan 10 22:55:41 but unless you want to customize it I'd suggest just installing the package via apt Jan 10 22:56:06 this pulls the necessary stuff from git, applies patches, configures and builds the kernel, and generates a debian package Jan 10 22:56:22 i need to customize it, because is for another board (close to bbb but different) Jan 10 22:56:59 (copy system.sh.sample to system.sh and tune it to taste, then ./build_deb.sh and time for coffee) Jan 10 22:57:00 will take a look, many thanks for the info. Jan 10 22:57:29 oh cool, thanks Jan 10 22:57:40 ehh, I mean ./build_deb.sh, wait for configuration menu, do your thing there, save&exit config and then time for coffee Jan 10 22:58:14 you can set AUTO_BUILD=1 in system.sh to skip being presented with config menu, but in your case you actually don't want that obviously Jan 10 22:58:45 nope, and I also need to add modify some drivers, but well, this is another thing Jan 10 22:58:52 really appreciated your help Jan 10 22:59:21 you're welcome Jan 10 22:59:55 veremit: interesting behaviour... http://pastebin.com/7XV7CJVa Jan 10 23:00:49 mmmm Jan 10 23:04:57 reading two memory locations exactly 4096 bytes apart over and over again... around 40 cycles per read (instead of the expected 1 cycle/read) Jan 10 23:13:58 jkridner: wanna see some weirdass results I got from a simple cache microbenchmark I did? -> http://pastebin.com/7XV7CJVa Jan 10 23:14:56 hmm, I should query some performance counters here to figure out what's going on Jan 11 00:01:33 hi all im trying to edit my uEnv.txt on newly flashed board. normally i mount /dev/mmcblk0p1 Jan 11 00:04:19 jenco: at least in recent kernels mmcblk0 would be the sd card Jan 11 00:06:55 also, if you have a question, consider asking it :) right now you just made two statements, and I'm really not sure how they are even related Jan 11 00:07:00 aaand gone Jan 11 00:07:28 jkridner: that. Jan 11 00:08:24 jkridner: ^ Jan 11 00:08:48 its exceedingly frustrating Jan 11 00:08:58 and just adds to the join/leave spam Jan 11 00:09:04 and doesn't really help *anyone* Jan 11 00:09:33 I have the join/leave spam on ignore, but that obviously has downsides too Jan 11 00:09:37 if you're not prepared to actually hang around to hear someone's answer .. it shows you really don't care . which belittles those who do contribute (regularly) here like zmatt and others :/ Jan 11 00:09:49 zmatt: right you don't *know* someone's left .. Jan 11 00:09:50 :/ Jan 11 00:09:59 which is why I insist on leaving it ON :/ Jan 11 00:10:32 that and complaining when some lunatic has client issues or connection problems lol Jan 11 00:10:53 I tried to figure out if it would be doable to make irssi ignore such traffic *unless* the user has talked in the last screenful or so Jan 11 00:10:55 I can stay connected for days/weeks .. why does everyone else have such problems?! Jan 11 00:11:05 zmatt: ooh, how far you get?! Jan 11 00:11:36 I find it easier to occasionally reply to a missing peep than endless seas of join/part spam. But to each their own and all. Jan 11 00:11:40 it didn't look good. definitely none of the many signal hooks are usable for this Jan 11 00:11:45 yeah ditto Jan 11 00:11:47 zmatt: yeah Jan 11 00:12:10 I also hate that ignore is applied to logs Jan 11 00:12:16 well I often get halfway through a reply .. and then jave to type well ** you tjhen Jan 11 00:12:21 ofc Jan 11 00:12:29 but not to the central channel logs ;P Jan 11 00:12:44 (when those work...) Jan 11 00:12:56 I've relegated join/leave to a feint grey so they#re tjere but less intrusive Jan 11 00:13:04 zmatt: they're frizty now too?! Jan 11 00:13:18 someone .. buy a new toaster ffs .. lol Jan 11 00:13:30 the fire alarm keeps going off ..hahaha! Jan 11 00:13:40 feint grey would still make relevant content scroll out of view Jan 11 00:13:50 zmatt: it does :( Jan 11 00:14:41 having it fade from the window or disappear and re-render the window would be ideal Jan 11 00:14:53 or I guess .. a subwindow might work Jan 11 00:15:09 or a tab between chat and modespam Jan 11 00:15:19 since all mine is timestamped anyhow Jan 11 00:15:46 that would be quite cool actually .. Jan 11 00:15:59 to be honest, just ignoring it works well enough that I'm rarely motivated to look into doing anything about it Jan 11 00:16:13 you could have (1) all together (2) separate join/leave/mode and chat Jan 11 00:16:25 (also... *fade*... don't you dare...) Jan 11 00:16:36 zmatt: hahaha :D Jan 11 00:16:53 I just ignore the channel now lol Jan 11 00:16:54 :P Jan 11 00:17:07 there are already a ton of websites where I use the user-css rule * { transition: none !important; } Jan 11 00:17:24 lol right Jan 11 00:17:29 the effect can be amazing Jan 11 00:17:46 and the gentoo folks complain about signal-to-noise ratio .. they have no *** clue ... lol Jan 11 00:17:51 like, holy crap everythign responds so fast Jan 11 00:18:03 :D Jan 11 00:18:20 it's as if things highlight *instantly* instead of taking noticable time to f... oh right Jan 11 00:18:36 :P Jan 11 00:18:40 zmatt: impatient?! :P Jan 11 00:18:42 lol Jan 11 01:48:58 Hey U of M Jan 11 01:49:13 howdy humerusj Jan 11 01:49:20 @jkridner how goes it? Jan 11 02:03:19 great. just finishing up the workshop. **** ENDING LOGGING AT Wed Jan 11 03:00:01 2017