DocScrutinizer05 changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
<mth> the one in arch/mips/boot/dts/
<viric> how does the build system know what dts to embed?
<viric> ah
fengling has joined #qi-hardware
fengling has quit [Ping timeout: 246 seconds]
wej has quit [Ping timeout: 272 seconds]
wej has joined #qi-hardware
Haswell has quit [Quit: Saliendo]
fengling has joined #qi-hardware
fengling has quit [Ping timeout: 264 seconds]
kristianpaul has quit [Quit: leaving]
kristianpaul has joined #qi-hardware
fengling has joined #qi-hardware
fengling has quit [Ping timeout: 246 seconds]
fengling has joined #qi-hardware
xiangfu has joined #qi-hardware
fengling has quit [Ping timeout: 265 seconds]
fengling has joined #qi-hardware
fengling has quit [Ping timeout: 240 seconds]
fengling has joined #qi-hardware
fengling has quit [Ping timeout: 244 seconds]
fengling has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
wpwrak has quit [Read error: Connection reset by peer]
<eintopf> nooooooo
wpwrak has joined #qi-hardware
mirko_ has joined #qi-hardware
apelete has quit [*.net *.split]
mirko has quit [*.net *.split]
apelete has joined #qi-hardware
fengling has quit [Ping timeout: 250 seconds]
fengling has joined #qi-hardware
fengling has quit [Ping timeout: 252 seconds]
fengling has joined #qi-hardware
dandon has quit [Quit: .]
Haswell has joined #qi-hardware
fengling has quit [Quit: WeeChat 1.0]
<viric> mth: I can't really find how the DTS gets embedded into the kernel
<viric> mth: what kernel option does that?
<larsc> BUILTIN_DTB
xiangfu has joined #qi-hardware
pcercuei has joined #qi-hardware
<viric> larsc: I can't find it for ARM. Is it only for mips?
<viric> nconfig → Search
Haswell has quit [Ping timeout: 264 seconds]
<larsc> ARM doesn't support built-in dtb
<mth> weird that that feature is arch-specific
<larsc> it needs low level support like the linker scripts and stuff
<pcercuei> larsc, quick question
<pcercuei> I read that devicetree is a way to describe the hardware, not the configuration of said hardware
<pcercuei> so what's the correct way to configure things like the clock map?
<larsc> what clock map?
<larsc> parent child relationship?
<pcercuei> yes
<pcercuei> and frequencies of PLLs
<larsc> yea, that's now in devicetree too...
<viric> larsc: aha, thank you.
<viric> damn arm. then I've to manually append the dtb to the kernel
<viric> before making the uboot image. is it?
<viric> So there isn't any config + "make" that builds a bootable ARM kernel anymore
<viric> it requires manual composing of the image
pcercuei has quit [Ping timeout: 252 seconds]
pcercuei has joined #qi-hardware
<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
<wpwrak> xiangfu: i wonder how i should refer to your group. "xiangfu and friends" ?
<xiangfu> the group named 'canaan creative'. :)
<wpwrak> "Creative + Share = Happy" hehe :)
<xiangfu> :)
Haswell has joined #qi-hardware
<wpwrak> diversifying from mining ? :)
<xiangfu> Yes.
<wpwrak> kewl !
<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
<wpwrak> it didn't sound very promising, with the falling btc value killing lots of mining companies
<wpwrak> btw, very pretty timeline on https://ehash.com/zh-hans/support/
<xiangfu> :)
<xiangfu> thanks.
<xiangfu> hmmm... should translate it to Englihs.
<xiangfu> wpwrak: I have learned a lot hardware/manufacture when doing this mining machine.
<xiangfu> what should I change on thresh in my boards? only PCB, no case?
<xiangfu> I tried put some plastics on top of the touch bar. it is hard to find out the good one.
pcercuei has quit [Remote host closed the connection]
pcercuei has joined #qi-hardware
<wpwrak> (thresh) maybe start with 500 then increase in large steps
<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.
<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.
<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.
<wpwrak> if the threshold is too high, no position marker appears at all or it flickers (rapidly appears and disappears)
xiangfu has quit [Remote host closed the connection]
pcercuei has quit [Ping timeout: 252 seconds]
pcercuei has joined #qi-hardware
kristianpaul has quit [Ping timeout: 255 seconds]
<arossdotme> should usb hubs have cap's? got a one here that have places for 2caps but there missing
<arossdotme> i forget the type name, you know the big blue non-smt type, the liquid sort
<wpwrak> almost all electronics have caps :) large electrolytic caps would be a bit unusual in a hub, but not impossible
<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
<wpwrak> e.g., i would expect a self-powered hub to have some silo caps on the power supply side.
<roh> hi there
<roh> i got a idea to bounce off you guys: what about a robots.txt for 'projects' ?
<roh> with all the project 'metadata' like contacts, project status, etc in machine readable, so distros/upstreams can import/source it
<wpwrak> who would use this metadata ? first time i see this kind of use of robots.txt
<roh> mainly for distros/downstream
<roh> to speed up the maintaining/security support
<wpwrak> so that would act as a sort of notification channel for urgent updates ?
<roh> like its now, but with the feature that you can update the links centrally
<roh> e.g. send updates via mailinglists, add an entry to the rss feed of your security incident site, and bump the version
<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
<wpwrak> i guess all contacts really boil down to the qi-hw mailing list :)
<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.
<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
<wpwrak> perhaps more importantly, how would it be populated ? i see some fields that would come from a commit hook, right ?
<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 ...
<pcercuei> lol
<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.
<arossdotme> wpwrak: thanks for the info.
<arossdotme> this as not externel powerr
<arossdotme> as=has
<arossdotme> I've got other ones with no external power
<arossdotme> and no caps
<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
<arossdotme> gta04
<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 ...
<arossdotme> ok
<arossdotme> thx for the info
<arossdotme> didn't know there was a limit in the usb stanard but me thinks it makes sense
<wpwrak> "The maximum load (CRPB) that can be placed at the downstream end of a cable is 10 µF in parallel with 44 Ohm." :)
<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.
<wpwrak> (the quote is from usb 2.0, page 177, "7.2.4.1 Inrush Current Limiting")
<arossdotme> ok
kristianpaul has joined #qi-hardware
dandon has joined #qi-hardware
qwebirc9174 has joined #qi-hardware
qwebirc9174 has quit [Client Quit]
wej has quit [Ping timeout: 250 seconds]
mithro has quit [Ping timeout: 250 seconds]
wej has joined #qi-hardware
mithro has joined #qi-hardware
Haswell has quit [Quit: Saliendo]
pcercuei has quit [Ping timeout: 265 seconds]