Topic for #qi-hardware is now 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
jekhor has quit [Ping timeout: 265 seconds]
pcercuei has quit [Ping timeout: 255 seconds]
LunaVorax has quit [Quit: Quitte]
sivoais is now known as _sivoais
urandom__ has quit [Quit: Konversation terminated!]
paroneayea has quit [Remote host closed the connection]
paroneay` has joined #qi-hardware
paroneay` is now known as paroneayea
paroneayea has quit [Changing host]
paroneayea has joined #qi-hardware
guanucoluis has quit [Ping timeout: 272 seconds]
guanucoluis has joined #qi-hardware
guanucoluis has quit [Ping timeout: 272 seconds]
pcercuei has quit [Quit: Bye]
dvdk has quit [Ping timeout: 244 seconds]
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer06 has joined #qi-hardware
emeb has quit [Quit: Leaving.]
wolfspra1l has joined #qi-hardware
wolfspraul has quit [Ping timeout: 248 seconds]
jekhor has joined #qi-hardware
jekhor has quit [Ping timeout: 264 seconds]
<kyak>
wpwrak: are you thinking about a particular use case for the SW UART?
<kyak>
is it possible to use it for serial console?
<kyak>
i mean, use UBB for serial console then
wolfspra1l has quit [Quit: leaving]
jluis has joined #qi-hardware
kilae has joined #qi-hardware
panda|x201 has joined #qi-hardware
porchao has joined #qi-hardware
lekernel has joined #qi-hardware
lekernel__ has quit [Ping timeout: 272 seconds]
DocScrutinizer06 is now known as DocScrutinizer05
<wpwrak>
kyak: (use case) yes, i want t use it to in-circuit program NXP LPC111x series MCUs. they use a surprisingly text-heavy protocol and it all goes over a UART.
<wpwrak>
it wouldn't work so well for a serial console (either end of it) since you always get small breaks where the receiver is not polling
<wpwrak>
for a driver that doesn't have this problem, things would have to move into the kernel, with an interrupt handler signaling the reception of a start bit
<wpwrak>
heard of it, yes. dunno. laptops didn't strike me as a big openness problem so far.
<wpwrak>
i.e., all the equipment i have does what it has to do without nasty closed source drivers or messy binary firmware. maybe there is binary firmware somewhere (though i don't think so) but it's handled transparently enough that i don't have to worry about it.
<wpwrak>
plus, a laptop is easily extended via USB, so - without any more specific requirements - there's not really a pressing need for having special built-in hardware features (such as expansion headers, fpgas, etc.)
<wpwrak>
plus, a laptop is a complex system, so this is a lot of work and it's expensive to make. not as bad as a smartphone, but substantial
<wpwrak>
ah, and my laptops have of course all intel graphics. no money wasted on nvidia or ati here. if they want to keep their products a secret, then they can keep their products ;-)
<kristianpaul>
thats a point need more openess, well you hack the pack but..
<wpwrak>
kristianpaul: one is some 4-5 years old (a fujitsu u1010), the other maybe 2 (an asus netbook)
<kristianpaul>
wpwrak: so you believe the history of restricted boot etc?
<kristianpaul>
or drm inside the processors..
<kristianpaul>
i would partially agree that laptops still fair open as the restrictions seems to be imposed somwhere else (tablets. for example)
<lindi->
I'd very much like to have a TPM to hold the hdd encryption keys of my laptop but I have a cheap model that doesn't support it
<lindi->
now it is quite trivial to bruteforce against my passphrase
<kristianpaul>
I do like that for portable harddrives
<wpwrak>
kristianpaul: my systems all predate restricted boot :)
<lindi->
I also think that RMS is doing more harm than good inventing these odd alternative terms :)
<kristianpaul>
okay lets wait some more years
<kristianpaul>
lindi-: he good point :)
<wpwrak>
kristianpaul: and i don't know of any DRM in my cpus either. of course, i stick with intel there.
<lindi->
wpwrak: I guess it depends on what you exactly count as DRM. do you include the SENTER instruction in your CPU?
<wpwrak>
hmm, don't even know what it is :)
<lindi->
wpwrak: it's a way to build dynamic root of trust: e.g. to make it possible for a userland process to operate on encryption keys even when rest of the system is compromised
<lindi->
wpwrak: SENTER instruction is like a normal branch except that it 1) disables other cores and interrupts 2) calculates a hash of the target code (up to 64KB) 3) tells the TPM that "we are now executing code that matches hash X and there is nothing that can interfere"
<lindi->
wpwrak: the TPM can then be told things like "please create a new RSA key and let only blocks with hashes X, Y and Z operate using it"
<lindi->
wpwrak: when you are done you execute the SEXIT instruction
<wpwrak>
nice. but as far as i know, there's no TPM in my machines. and if there's anything like that, it's dormant. i.e., i had no troubles installing linux.
<lindi->
yeah you need several primitives to make anything useful with SENTER
<lindi->
wpwrak: if you want to hear more about the positive uses of these technologies I suggest reading about http://qubes-os.org/trac
<wpwrak>
yeah,even the most vile technology can have good uses :)
xiangfu has quit [Ping timeout: 252 seconds]
<wpwrak>
i do wonder whether it's worth the effort to worry about things at such a low level. i mean, apart from academic interest and the tin foil hat faction.
<lindi->
wpwrak: well I'm just interested in the technology and want to know what is possible
xiangfu has joined #qi-hardware
freemor has joined #qi-hardware
xiangfu has quit [Ping timeout: 255 seconds]
freemor has quit [Ping timeout: 272 seconds]
GNUtoo-desktop has quit [Quit: [INFO] fsogsmd : received signal -11, exiting.]
freemor has joined #qi-hardware
erikkugel has joined #qi-hardware
Hoolxi has joined #qi-hardware
Hoolxi has quit [Read error: Connection reset by peer]
GNUtoo has joined #qi-hardware
rz2k has joined #qi-hardware
freemor2 has joined #qi-hardware
freemor has quit [Ping timeout: 252 seconds]
freemor2 has quit [Ping timeout: 265 seconds]
freemor has joined #qi-hardware
freemor has quit [Ping timeout: 272 seconds]
emeb has joined #qi-hardware
jluis has quit [Remote host closed the connection]
freemor has joined #qi-hardware
freemor has quit [Client Quit]
jekhor has joined #qi-hardware
pcercuei has joined #qi-hardware
pcercuei has quit [Read error: Connection reset by peer]
dandon_ has joined #qi-hardware
dandon has quit [Ping timeout: 244 seconds]
dandon_ is now known as dandon
LunaVorax has joined #qi-hardware
jekhor has quit [Ping timeout: 255 seconds]
unclouded has joined #qi-hardware
rz2k has quit []
paroneayea has quit [Ping timeout: 264 seconds]
GNUtoo has quit [Ping timeout: 248 seconds]
paroneayea has joined #qi-hardware
LunaVorax has quit [Ping timeout: 252 seconds]
jekhor has joined #qi-hardware
Jurting has joined #qi-hardware
GNUtoo has joined #qi-hardware
Kikdo has joined #qi-hardware
Kikdo has quit [Client Quit]
jekhor has quit [Ping timeout: 252 seconds]
kilae has quit [Quit: ChatZilla 0.9.89 [Firefox 17.0.1/20121128204232]]
erikkugel has left #qi-hardware [#qi-hardware]
guanucoluis has joined #qi-hardware
LunaVorax has joined #qi-hardware
Jurting has quit [Remote host closed the connection]
Jurting has joined #qi-hardware
GNUtoo has quit [Quit: Program received signal SIGSEGV, Segmentation fault.]
xiangfu has joined #qi-hardware
pcercuei has joined #qi-hardware
LunaVorax has quit [Quit: Quitte]
pcercuei has quit [Remote host closed the connection]