**** BEGIN LOGGING AT Wed Nov 18 03:02:03 2020 Nov 18 03:29:55 Anyway, forget it. I know this, as usual, is not a BBB related issue. I should read about backporting ideas for ammhf on Stretch for this effort. Nov 18 04:15:16 hey hey Nov 18 04:15:34 anyone try out lorfor linux compatibility layer thing Nov 18 04:16:07 for the bbai Nov 18 06:38:16 Hi Nov 18 06:38:20 Hi Nov 18 06:38:45 Can anyone guide me how to contri Nov 18 18:44:09 lorfor Nov 18 18:44:12 oooh Nov 18 18:44:35 I'm calling this a basic guide to linux on arm Nov 18 18:44:39 but i'm not sure thats the best description Nov 18 18:44:42 its literally just a concept over Nov 18 18:44:47 could use feedback if anyone could spare some Nov 18 18:44:52 https://docs.google.com/presentation/d/1RTJVGqengvrujywzD16YsCD7UGrFinIgLuLo6GUIrPk/edit?usp=sharing Nov 18 18:44:58 comments are open Nov 18 19:01:58 i really should iterate on that before i send it to anyone Nov 18 19:53:20 im stuck... seems the tilcdc driver may be borked Nov 18 19:53:58 but really, i don't wanna go about recompiling kernel again.. Nov 18 19:54:24 running into this issue it seems:https://cospandesign.github.io/linux,am335x/2018/10/16/am335x-lcd-panel.html Nov 18 20:07:21 anyone have any luck loading framebuffers in the latest kernels? Nov 18 21:07:35 why recompile the kernel for tilcdc? functions well as a module Nov 18 21:08:20 i haven't in latest kernels but i've done tons of stuff w/ it in general Nov 18 21:11:25 it's by default built into the kernel. you would need to recompile to get it as module right? Nov 18 21:11:59 I am having trouble getting a newhaven display working on 4-19 keep failing to instantiate a fb driver Nov 18 21:12:28 the design is basically this: https://github.com/beagleboard/devicetree-source/blob/master/arch/arm/boot/dts/BB-BONE-LCD7-01-00A3.dts Nov 18 21:12:48 but fb never appears due to same errors in the blog post above. Nov 18 21:20:59 haha, also managed to make a pretty reliable boot loop with my device tree overlay. Nov 18 21:30:18 Alright, what I have learned... hopefully it's true, is that the tilcdc-panel driver has no means of specifying a port , which the current fb driver needs to say " hey, create a fb device" Nov 18 21:40:42 i never went through this Nov 18 21:41:01 i have no idea how to create fb devices w/ wayland Nov 18 21:41:29 but i mean you dot need to to just test an LCD Nov 18 21:47:05 hey Konagnxx Nov 18 21:47:15 you on a black or AI Nov 18 21:47:31 I had the new haven working on the black that ks to zmatt Nov 18 21:47:42 thanks to zmatt Nov 18 21:47:50 have to void the warranty though Nov 18 21:48:09 black Nov 18 21:48:11 ayjay_t: I meant lorforlinux Nov 18 21:48:28 hahahah already cut some traces to get rid of pesky emmc Nov 18 21:48:47 he has a google summer of code project on the compatibility layer Nov 18 21:49:06 Konagnxx: than I probably cannot help Nov 18 21:49:19 though mine worked after that one change Nov 18 21:49:24 have full function Nov 18 21:49:30 no need, it was to get wifi working .. what did you do? Nov 18 21:49:51 take out the R1 resistor Nov 18 21:50:25 do you happen to know which resistor that is? as in what its function is? Nov 18 21:51:09 I have a strong feeling that is not the issue i have as i am not getting any fb driver being registered/ no pins are wiggling. Nov 18 22:03:51 I could not even turn on the screen Nov 18 22:04:09 I just power cycled. zmatt would have to explain I am a noob Nov 18 22:04:22 I just chimed in since I stuggled with their product Nov 18 22:05:44 if you're talking about the thing I'm thinking about, it was enabling the backlight at power-on (instead of leaving it off until enabled by software) and the in-rush current right at the moment of power on was causing overcurrent resulting in power-off Nov 18 22:06:48 that's the only issue I remember of anyone having to do with a resistor on an lcd cape Nov 18 22:09:19 ayjay_t: "i have no idea how to create fb devices w/ wayland" what do you mean _create_ fb devices with wayland? that's like saying "I have no idea how to create a nail using a hammer" Nov 18 22:11:56 i wouldn't be wrong then would i Nov 18 22:12:14 how did wayland enter the discussion anyway? Nov 18 22:12:32 i dunno i mean we keep on talking about "creating db devices" Nov 18 22:12:48 i thought this was an issue of an API change i wasn't aware of Nov 18 22:12:57 because i always found a /dev/fbX ready to go Nov 18 22:13:16 creating db ---> creating fb Nov 18 22:14:34 it shows up if the driver loads and modesetting has been done (based on EDID or fixed configuration) Nov 18 22:15:54 does wayland even support the legacy fbdev? I'd assume it requires a drm device Nov 18 22:16:50 but you can create nails with hammers... Nov 18 22:16:51 yeah thats what i thought too, both those things Nov 18 22:17:00 :P Nov 18 22:17:32 which is why i thought we were trying to load some driver that a) drives the lcd tlcdc or w/e, and then also load another driver that provides an interface with fbdev Nov 18 22:17:42 i honestly have no idea how to paint the screen manually w/ layland Nov 18 22:17:46 wayland* Nov 18 22:18:07 ds2: lol i still dont know how Nov 18 22:18:21 oh nvm, if you gave me hot enough metal and a nice hammer i bet i could make a nail Nov 18 22:18:25 again, how did wayland enter the discussion, is Konsgnxx using wayland? Nov 18 22:18:34 no i guess not, i made that assumption Nov 18 22:18:50 or i mean maybe he is Nov 18 22:19:03 I doubt it Nov 18 22:19:04 all early nails were made with iron, forge, and a hammer Nov 18 22:19:11 ds2: shush :P Nov 18 22:20:01 ayjay_t: and not sure what you mean by "paint the screen manually w/wayland" .. either you're painting the screen manually or something (like wayland or X11) is painting the screen for you Nov 18 22:20:13 they're kinda mutually exclusive Nov 18 22:20:40 sorry when i say "manually" i mean like how i used to just output a bitmap to fbdev Nov 18 22:21:27 (as opposed to using some kind of window layer or graphics layer) Nov 18 22:22:02 I mean, if you're using wayland there's inherently "some kind of window layer" Nov 18 22:22:29 yeah i knew wayland took a different approach Nov 18 22:22:38 i dont know what the newest BBB deployments use Nov 18 22:22:38 I mean, same for X11 Nov 18 22:22:48 the default BBB image doesn't include a gui Nov 18 22:23:27 but what i really mean is, again, i dont know what the equiv. of "writing a bitmap to /dev/fb0" would be in wayland Nov 18 22:28:34 I think wayland gives you a drm buffer to render into Nov 18 22:28:45 not completely sure, never dug into it Nov 18 22:28:50 huh yah Nov 18 22:28:51 I do know wayland doesn't really have a rendering API itself Nov 18 22:29:32 "A buffer provides the content for a wl_surface. Buffers are created through factory interfaces such as wl_drm, wl_shm or similar. It has a width and a height and can be attached to a wl_surface, but the mechanism by which a client provides and updates the contents is defined by the buffer factory interface." Nov 18 22:36:42 wl_shm seems simple enough, it lets you create a memory pool you share with the wayland server from which you can carve out one or more buffers which you can render into and submit to wayland Nov 18 23:47:36 so I got the fan cape and the bbai still sluggish Nov 19 00:00:12 is there like a benchmark tool for this thing kinda like they have for gfx cards Nov 19 00:33:41 mattb000ne: Did you try to follow /upgrade on the beagleboard.org site? Nov 19 00:34:03 I think that is supposed to get you up to speed and lesson the cpu burden. I thougth so. Nov 19 01:42:13 MattB0ne_: are you also mattb000ne? Nov 19 02:32:02 GenTooMan: Do you ever use KiCAD to make a 3D image of a Cape for the BBB? Nov 19 02:32:49 I am trying now. It does not allow me to pick the current image with the two layers. Nov 19 02:34:29 I am Nov 19 02:34:39 I have my phone and comp logged in Nov 19 02:47:51 GenTooman: I am asking b/c I have a Cape schematic in a .kicad_pcb but not in net_list. Nov 19 02:48:17 The only one I have in net_list is "one" header. Nov 19 02:58:04 But...the entire Cape is already done. I picked it up in '15 (I think). **** ENDING LOGGING AT Thu Nov 19 02:59:59 2020