| 00:00.16 | mth | the one in arch/mips/boot/dts/ |
| 00:11.26 | viric | how does the build system know what dts to embed? |
| 00:11.56 | viric | ah |
| 00:32.39 | *** join/#qi-hardware fengling (~fengling@60.14.88.170) |
| 01:23.48 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 01:47.45 | *** join/#qi-hardware fengling (~fengling@60.14.88.30) |
| 02:14.00 | *** join/#qi-hardware kristianpaul (~kristianp@181.137.231.189) |
| 02:14.01 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 02:18.14 | *** join/#qi-hardware fengling (~fengling@60.14.88.30) |
| 03:42.00 | *** join/#qi-hardware fengling (~fengling@60.14.88.30) |
| 03:56.08 | *** join/#qi-hardware xiangfu (~xiangfu@60.194.113.42) |
| 04:13.00 | *** join/#qi-hardware fengling (~fengling@60.14.88.30) |
| 04:28.51 | *** join/#qi-hardware fengling (~fengling@60.14.88.30) |
| 06:04.08 | *** join/#qi-hardware fengling (~fengling@60.14.88.30) |
| 07:15.23 | eintopf | nooooooo |
| 07:18.25 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 07:22.08 | *** join/#qi-hardware mirko_ (~mirko@217.115.11.26) |
| 07:35.56 | *** join/#qi-hardware apelete (~apelete@176-26-190-109.dsl.ovh.fr) |
| 08:19.54 | *** join/#qi-hardware fengling (~fengling@60.14.88.30) |
| 08:40.37 | *** join/#qi-hardware fengling (~fengling@60.14.88.30) |
| 09:01.21 | *** join/#qi-hardware Haswell (~Haswell@unaffiliated/haswell) |
| 10:21.13 | viric | mth: I can't really find how the DTS gets embedded into the kernel |
| 10:21.17 | viric | mth: what kernel option does that? |
| 10:47.39 | larsc | BUILTIN_DTB |
| 10:52.25 | *** join/#qi-hardware xiangfu (~xiangfu@60.194.113.42) |
| 11:02.04 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118::5) |
| 11:20.06 | viric | larsc: I can't find it for ARM. Is it only for mips? |
| 11:20.13 | viric | nconfig â Search |
| 12:10.44 | larsc | ARM doesn't support built-in dtb |
| 12:14.21 | mth | weird that that feature is arch-specific |
| 12:16.11 | larsc | it needs low level support like the linker scripts and stuff |
| 12:19.31 | pcercuei | larsc, quick question |
| 12:19.59 | pcercuei | I read that devicetree is a way to describe the hardware, not the configuration of said hardware |
| 12:20.48 | pcercuei | so what's the correct way to configure things like the clock map? |
| 12:27.25 | larsc | what clock map? |
| 12:27.34 | larsc | parent child relationship? |
| 12:27.45 | pcercuei | yes |
| 12:27.56 | pcercuei | and frequencies of PLLs |
| 12:28.23 | larsc | yea, that's now in devicetree too... |
| 12:30.24 | viric | larsc: aha, thank you. |
| 12:30.41 | viric | damn arm. then I've to manually append the dtb to the kernel |
| 12:30.46 | viric | before making the uboot image. is it? |
| 12:34.55 | viric | So there isn't any config + "make" that builds a bootable ARM kernel anymore |
| 12:35.03 | viric | it requires manual composing of the image |
| 12:36.47 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118:1af4:6aff:fec5:1c8f) |
| 12:37.35 | wpwrak | xiangfu: i'm about to write a quick update on what has happened in the anelok world in the last week and i'd like to also mention your boards, e.g., with this picture: http://downloads.qi-hardware.com/people/xiangfu/anelok/tmp/Anelok-booting.jpg |
| 12:38.14 | wpwrak | xiangfu: i wonder how i should refer to your group. "xiangfu and friends" ? |
| 12:55.51 | xiangfu | the group named 'canaan creative'. :) |
| 13:24.14 | wpwrak | "Creative + Share = Happy" hehe :) |
| 13:25.42 | xiangfu | :) |
| 13:26.34 | *** join/#qi-hardware Haswell (~Haswell@unaffiliated/haswell) |
| 13:29.20 | wpwrak | diversifying from mining ? :) |
| 13:30.41 | xiangfu | Yes. |
| 13:35.23 | wpwrak | kewl ! |
| 13:36.04 | wpwrak | when i read about the what's going on in the btc world these days, i was actually wondering how that mining business must be going |
| 13:36.29 | wpwrak | it didn't sound very promising, with the falling btc value killing lots of mining companies |
| 13:37.18 | wpwrak | btw, very pretty timeline on https://ehash.com/zh-hans/support/ |
| 13:44.18 | xiangfu | :) |
| 13:44.46 | xiangfu | thanks. |
| 13:45.07 | xiangfu | hmmm... should translate it to Englihs. |
| 13:50.01 | xiangfu | wpwrak: I have learned a lot hardware/manufacture when doing this mining machine. |
| 13:52.02 | xiangfu | what should I change on thresh in my boards? only PCB, no case? |
| 13:53.19 | xiangfu | I tried put some plastics on top of the touch bar. it is hard to find out the good one. |
| 15:35.54 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118::5) |
| 16:03.16 | wpwrak | (thresh) maybe start with 500 then increase in large steps |
| 16:05.03 | wpwrak | (board & case) the mentioning of board and case in the comments is just that - a comment. the information isn't used anywhere. so you can use whatever you like there. similar for the "name" field. you can also just not set a name. |
| 16:07.09 | wpwrak | (finding plastic) yeah, it'll be total guesswork :) but don't worry. tuning the slider is no exact science. just set a value, see how it responds, then adjust, and so on. |
| 16:08.58 | wpwrak | if the threshold is too low, then the position indicator appears before you have a proper touch. e.g., when the finger is just approaching the sensor or when you touch it very lightly. also, when pushing harder, the position marker will move a fair bit as pressure increases. |
| 16:09.49 | wpwrak | if the threshold is too high, no position marker appears at all or it flickers (rapidly appears and disappears) |
| 16:43.14 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118:1af4:6aff:fec5:1c8f) |
| 17:24.10 | arossdotme | should usb hubs have cap's? got a one here that have places for 2caps but there missing |
| 17:25.02 | arossdotme | i forget the type name, you know the big blue non-smt type, the liquid sort |
| 17:34.07 | wpwrak | almost all electronics have caps :) large electrolytic caps would be a bit unusual in a hub, but not impossible |
| 17:34.53 | wpwrak | and if they're missing, perhaps it doesn't need them :) could be that the same pcb is used in different products / modes of operation |
| 17:35.29 | wpwrak | e.g., i would expect a self-powered hub to have some silo caps on the power supply side. |
| 17:56.15 | roh | hi there |
| 17:56.46 | roh | i got a idea to bounce off you guys: what about a robots.txt for 'projects' ? |
| 17:57.29 | roh | with all the project 'metadata' like contacts, project status, etc in machine readable, so distros/upstreams can import/source it |
| 17:57.52 | roh | just a rfc: http://pastebin.com/7yERKj1t |
| 18:02.02 | wpwrak | who would use this metadata ? first time i see this kind of use of robots.txt |
| 18:02.34 | roh | mainly for distros/downstream |
| 18:03.02 | roh | to speed up the maintaining/security support |
| 18:03.43 | wpwrak | so that would act as a sort of notification channel for urgent updates ? |
| 18:04.17 | roh | like its now, but with the feature that you can update the links centrally |
| 18:04.43 | roh | e.g. send updates via mailinglists, add an entry to the rss feed of your security incident site, and bump the version |
| 18:06.12 | roh | also a downstream user would have a defined place to find stuff like security contacts. i also imagine its easy to integrate into stuff like launchpad and ticketing systems |
| 18:06.45 | wpwrak | i guess all contacts really boil down to the qi-hw mailing list :) |
| 18:07.46 | roh | imagine you would need to find a specific security contact for a piece of code in your distro and you want to mail the maintainer, the security contact and the distros security contact.. thats 3 manual to search mailaddresses. or a lookup in 2 textfiles. |
| 18:09.48 | wpwrak | yeah, i'd expect the each distro to compile this sort of information in whatever format they use. well, that could of course come from a robots.txt, if anyone actually thinks of looking there |
| 18:10.23 | wpwrak | perhaps more importantly, how would it be populated ? i see some fields that would come from a commit hook, right ? |
| 18:13.59 | wpwrak | hmm, interesting. neighbours a few floors down are busy painting a visibly dirty terrace floor. first i thought they were just cleaning it, but then the inside of the water bucket wouldn't be all red ... |
| 18:14.48 | pcercuei | lol |
| 18:25.36 | arossdotme | robots.txt is a web thing. it's for search engines, in the file you say if you mind them indexing this or that. |
| 18:25.50 | arossdotme | wpwrak: thanks for the info. |
| 18:26.05 | arossdotme | this as not externel powerr |
| 18:26.12 | arossdotme | as=has |
| 18:26.30 | arossdotme | I've got other ones with no external power |
| 18:26.34 | arossdotme | and no caps |
| 18:27.25 | arossdotme | I plan to use one powered from a usb power bank battery to power a usb hub and devices, with my zipit pocket compute rand my gtao4 |
| 18:27.29 | arossdotme | gta04 |
| 18:29.58 | wpwrak | bus-powered hubs can't have a lot of caps because the usb standard limits the capacitive upstream load. i mean, you could have massive caps behind a big resistor, but why bother. and the few hundred uF you'll want in your design in total don't really need electrolytic caps. well, if you really *like* them, you can of course use such critters ... |
| 19:00.40 | arossdotme | ok |
| 19:01.06 | arossdotme | thx for the info |
| 19:01.35 | arossdotme | didn't know there was a limit in the usb stanard but me thinks it makes sense |
| 19:05.45 | wpwrak | "The maximum load (CRPB) that can be placed at the downstream end of a cable is 10 µF in parallel with 44 Ohm." :) |
| 19:06.30 | wpwrak | so the 44 Ohm would be the "big" resistor. behind it you can put as many caps as you like, but they'll charge slowly. |
| 19:07.05 | wpwrak | (the quote is from usb 2.0, page 177, "7.2.4.1 Inrush Current Limiting") |
| 19:18.00 | arossdotme | ok |
| 20:05.18 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 21:16.07 | *** join/#qi-hardware dandon (~dandon@88.151.75.119) |
| 21:46.49 | *** join/#qi-hardware qwebirc9174 (5dc6a3bb@gateway/web/freenode/ip.93.198.163.187) |
| 22:25.31 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a08c:1::6e) |
| 22:49.04 | *** join/#qi-hardware mithro (sid24875@gateway/web/irccloud.com/x-dbjghxtqilmxpnnx) |
