#qi-hardware IRC log for Thursday, 2012-10-11

wpwrakyeah, the spammers removed quite a few words from the written english language.00:02
arossDOTmehmm the smaller posts ant got though yet. I guess I just wait.00:08
kristianpaulha nice wr703n was reversed eng01:22
kristianpaulafaik not a free cad..01:23
wolfspraulkristianpaul: links?02:34
kristianpaulwolfspraul: http://dangerousprototypes.com/2012/10/10/reverse-engineering-layout-of-tp-link-tl-wr703n-802-11n-router/03:05
wolfspraulhe :-)03:29
wolfspraulthey worry whether it is 'legal' to do this. that discussion seems to be more important than this 'layout' only covering the top and bottom side and not the internal layers03:29
wolfspraulurgh :-)03:29
wolfspraulopen hardware at its finest03:29
wolfsprauland then the non-functional 2-layer 'layout' is dumped into eagle03:30
wolfspraulha ha03:30
wolfspraulpainful stuff03:30
wolfspraulI'm sure the industry is shivering in fear of that competitive threat there03:31
wolfspraulit reminds me of some sloppily taken and blurred pictures of a pcb that some other project posted as proof of their 'openess' a while ago03:32
wolfspraulthey should take the whole pcb apart, photograph and enter into kicad/geda all layers, measure the values of all components and create an equivalent schematic03:32
wolfspraulthe they should proceed with a little 'couple hundred' test run to fix some bugs03:33
wolfsprauland finally they could think about how to make money with an item that sells for 16 USD / pc, including box, case, usb cable, power adapter, etc. etc.03:33
wolfspraulso looking at all this, I guess a quick couple-hour job dumping 2 layers into eagle and posting something is all we can and should expect03:33
wolfspraulI'm curious how tp-link develops the sub-20 USD computer category that they have there...03:34
wolfspraulI have a whole bunch of these 703n around me, as wifi repeaters and what not03:34
rohwolfspraul: how? copy-paste copy-paste copy-paste03:46
rohand that done by people who can work for ridicilous low wages03:46
wpwrakthat's the fab. but behind that, you need some engineers who are very good. ultra-low price means huge volume. huge volume means very little room for errors.03:49
rohwpwrak: thats what we think, from our pov. i guess there are different ones, else people wouldnt try to competen in 16E hw builing and sales03:50
rohi know i dont. nothing to win there.03:50
wpwrakwhy shouldn't they ? if they're good enough, and have access to the production capability (including ramp-up monay), they can pull it off.03:51
rohwolfspraul: btw.. i did some 'powertools (vibration sander) and pcb tests... not as difficult as it sounds. atleast a 4layer board is a thing of one night and a bit of patience03:51
wpwrakmeanwhile, the giants are trying to kill each other in the high-end market ...03:52
rohwpwrak: still its single euros per device. and huge risks. so from my pov its bad business.03:52
wpwrakdinosaurs fighting dinosaurs, while the rodents happily evolve ahead :)03:52
rohnot that i dont like hw so cheap, but i cannot recommend anybody competing there03:52
wpwrakwe can't compete. but that doesn't mean that others have the same limitation.03:53
rohwpwrak: may be. but thats not my concern then 03:53
wolfspraullet's see whether the market is big enough that qualcomm comes out with nice integrated follow-on chips for that segment03:57
wpwrakit's probably just a question of having enough money at hand. if you can afford to produce 10M units before seeing any revenue, and the occasional mishap (oops, we just made one cubic kilometer of worthless trash) won't kill you, then you're big enough to play that game.03:57
wolfspraulthat's pretty much the only moving piece, and it would be nice if they would, no?03:57
wolfspraulyeah the economics are pretty amazing if you really wrap your head around it03:58
wolfspraul*selling* a whole computer with box, usb cable, power adapter, etc. etc. for 16 USD retail?03:58
wolfspraulthat's unbelievable really03:58
wolfsprauleven the tiniest expenses of 1 full-time engineer working on something for a while will need big big volume to be recouped03:58
wolfspraulI hope they sell those thingies in the tens of millions and qualcomm can come out with improved chips, would be cool still03:59
wpwrakhmm, i think all that only works at numbers where you can easily afford a bunch of really good engineers03:59
wolfspraulthe numbers are just amazing I think04:00
wolfspraulit's under-appreciated as an economic achievement04:00
wolfspraultry to buy an iron, and you will be hard pressed to find one below 20 USD04:00
wpwrakyeah, a bit beyond our league. at least we understand enough of all that to be impressed :)04:00
wolfspraulbtw, fpgatools reached 20k lines of code today, phew :-)04:06
wolfspraultowards the blinking led...04:06
wolfspraulI hope this is all the right way to do it, but I can only try...04:07
wpwrakdamn. you beat fped (19.5 klocs)04:12
roh*sigh* quite depressing. i designed a series of devices lately and currently i can't even afford to prototype em04:17
rohand thats simple crap. i got variants in dip and smd, and made a modular one last04:18
rohcould be sold as kit, but i need to invest a few hundred euro for parts and pcbs to be made and invest another bunch of time into software and finalisation of the mechanics/case04:19
roheven to get that back the devices would need to be much more expensive that such a router, even if they are much simpler. sucks.04:19
rohits a modular spdif routing/mux equipment which uses structured cat5 cabling as backend04:20
kyakxiangfu: hi, could we please catch up with the latest openwrt, there are several important commits there (which allow us to use gettext at it's power)?08:50
qi-bot[commit] nbd: lua: enable parallel builds (master) http://qi-hw.com/p/openwrt-xburst/4d8413110:11
qi-bot[commit] florian: [package] base-files: skip LEDs handled by rssileds in led init-script (master) http://qi-hw.com/p/openwrt-xburst/8bbe39a10:11
qi-bot[commit] florian: [ar7] generate vmlinux.srec and vmlinux.bin from srec2bin (master) http://qi-hw.com/p/openwrt-xburst/c8c0e0c10:11
qi-bot[commit] kaloz: [cns3xxx]: fix non terminated uart resources for laguna (master) http://qi-hw.com/p/openwrt-xburst/6c1258a10:11
qi-bot[commit] kaloz: The Gateworks System Controller (GSC) is an i2c device that provides system (master) http://qi-hw.com/p/openwrt-xburst/228bf4d10:11
qi-bot[commit] kaloz: [cns3xxx]: fix (really this time) laguna UART config (master) http://qi-hw.com/p/openwrt-xburst/b2305bd10:11
qi-bot[commit] Xiangfu Liu: uboot-xburst: update to 2010.06 (master) http://qi-hw.com/p/openwrt-xburst/a79283a10:11
qi-bot[commit] Xiangfu Liu: uboot-xburst: enable-silent-console.patch (master) http://qi-hw.com/p/openwrt-xburst/33d9b4c10:11
qi-bot[commit] Xiangfu Liu: uboot silent console (master) http://qi-hw.com/p/openwrt-xburst/0bc736c10:11
qi-bot[commit] Xiangfu Liu: uboot-xburst: change load kernel size (master) http://qi-hw.com/p/openwrt-xburst/7e159dc10:11
qi-bot[commit] Xiangfu: xburst: add WPAN support (master) http://qi-hw.com/p/openwrt-xburst/2ed90f610:11
qi-bot[commit] Xiangfu Liu: add WPAN(atben,atusb) kernel module file thansk blogic #qi-hardware @freenode.net (master) http://qi-hw.com/p/openwrt-xburst/32b4b0610:11
qi-bot[commit] Xiangfu: xburst qi_lb60 disable WPAN kernel options, should build as module (master) http://qi-hw.com/p/openwrt-xburst/804038710:11
qi-bot[commit] Xiangfu: xburst: add Ben NanoNote kernel logo (master) http://qi-hw.com/p/openwrt-xburst/875b42110:11
qi-bot[commit] Xiangfu: xburst: qi_lb60 select the nanonote slash screen (master) http://qi-hw.com/p/openwrt-xburst/07a3c5d10:11
qi-bot[commit] Xiangfu: WPAN kernel module: make atusb depends on at86rf230 (master) http://qi-hw.com/p/openwrt-xburst/f6662d110:11
qi-bot[commit] Xiangfu: WPAN: fix atusb cannot build as module (master) http://qi-hw.com/p/openwrt-xburst/ce4eb6a10:11
qi-bot[commit] Xiangfu: WPAN: wpan.mk: fix typo, add other IEE802154 device to WPAN subment (master) http://qi-hw.com/p/openwrt-xburst/381aece10:11
qi-bot[commit] Xiangfu: xburst: ben nanonote: add modifire keys and fbcon-color patches (master) http://qi-hw.com/p/openwrt-xburst/a53d7e810:11
qi-bot[commit] Xiangfu: uboot-xburst: update to v2012.10-rc2 (master) http://qi-hw.com/p/openwrt-xburst/af862e910:11
kyakxiangfu: lot's of thanks10:30
xiangfukyak, HI. I plan to release image soon. this week. 11:07
xiangfukyak, thanks for the info. so I re-start the build after saw your message.11:07
kyakxiangfu: i hope qt/gtk will make into image this time :)11:09
xiangfugtk get back.11:10
kyakdid you disable xorg feed for a special reason?11:10
xiangfubut qt still fail to build.11:10
kyakdo yo uplan to release with 3.6 kernel?11:10
xiangfukyak, no. the release build goes 2 steps. 1. build minimal. save all failed packages. 2. build full_system. dis-select all failed packages.11:10
xiangfukyak, (linux 3.6) no. I will follow the OpenWrt upstream. now the OpenWrt still 3.311:11
xiangfukyak, the uboot is update to v2012.10, and fixed boot from memcard.11:12
kyakthat's good11:12
kyakso let's see how many fallouts we got..11:12
kyaki'm building the full image as well11:12
kyakxiangfu: for xorg, i'm just reminding that you've disabled xorg feed completely from feeds.conf11:14
kyakqt4 is in that feed.11:14
kyakand gtk as well11:15
xiangfuno. checkout: http://fidelio.qi-hardware.com/~xiangfu/openwrt-xburst.full_system/feeds.conf11:15
xiangfuif we disable the xorg feed. openwrt does not know there is qt libs etc.11:16
xiangfuthere is the failed build package so far: http://fidelio.qi-hardware.com/~xiangfu/building/Nanonote/Ben/failed_packages.txt11:17
xiangfudavid's liballegro and emacs failed to build. :(11:17
kyakxiangfu: i'm talking about this http://projects.qi-hardware.com/index.php/p/openwrt-packages/source/file/master/nanonote-files/data/qi_lb60/conf/feeds.conf11:17
xiangfuoh. 11:18
kyakif qt4 failed, qt4 packages should have failed as well11:18
kyakperhaps it's a false positive with qt411:19
xiangfuthen I must make some mistake on copy feeds.conf to final folder.11:19
xiangfukyak, oh. sorry for confuse. 11:19
xiangfukyak, I stop use that file for long time.11:19
xiangfukyak, I think we just drop it from openwrt-packages.11:20
xiangfukyak, since we already keep a correct file under "http://downloads.qi-hardware.com/software/images/Ben_NanoNote_2GB_NAND/'11:20
kyakthis makes sense.. need to correct http://en.qi-hardware.com/wiki/Building_Software_Image wiki page11:21
kyakit refers to feeds.conf from openwrt-packages11:21
xiangfuI plan to keep that in git history. but that do needs more time compare to keep it under downloads.qi-hardware.com11:22
qi-bot[commit] Xiangfu: nanonote-files: remove outdate feeds.conf (master) http://qi-hw.com/p/openwrt-packages/54915fa11:22
kyakwe will refer to http://downloads.qi-hardware.com/software/images/NanoNote/Ben/latest/feeds.conf11:23
kyaki updated the wiki11:24
xiangfukyak, great. thanks.11:24
kyakxiangfu: how do you deselect failed packages? mark them as =m?11:27
xiangfukyak, http://fidelio.qi-hardware.com/~xiangfu/build-scripts/patch-openwrt.sh11:28
xiangfuthe 'failed_packages.txt' created when compile openwrt minimal11:29
kyakbasically such approach should produce an empty failed_packages.txt at the end11:29
kyakwhen all failed are marked as =m11:30
kyaki'm asking because the final failed_packages.txt doesn't show ALL the failed packages11:30
xiangfuif failed packages mark as =m. it still have 'failed build ....' in BUILD_LOG.11:36
xiangfuit basically make the full_system compile smooth.11:36
kyakhave a look at NanoMap, tile, qball.. they are =m, but not exist in failed_packages11:37
kyakthough they definitely failed11:37
kyakas they don't exist in packages/11:37
xiangfucurrect 'failed_packages.txt' not include all failed packages because the openwrt_minimal failed and exit build.11:39
xiangfuthis is because the 'qemu-host' failed to build. even if I mark it as 'm'. it still break the build.11:39
kyaki'm talking about the release11:39
kyakah damn11:40
kyaki need new eyes11:40
kyakok, http://downloads.qi-hardware.com/software/images/NanoNote/Ben/latest/failed_packages.txt is much better11:40
kyakmany failed packages, just as expected :) sorry for confusion11:40
xiangfuyes. that build take my too much time. so I come with this auto mark failed package as modular. recently. :)11:41
kyakthat's good!11:41
xiangfuthis whole build take ~80 hours. :-) but it build smooth which is good. 11:42
xiangfuand I think I have a lot of 80 hours between release. :-)11:42
kyakstrange, now 'make' fails at 'make[3] -C target/linux compile'. When i re-run as 'make V=s', i'm presented with kernel config and then the build goes on11:42
kyakrunning make kernel_menuconfig to update our config doesn't seem to help11:43
kyaki never observed inconsistency between make and verbose make before11:43
kyakperhaps kernel_menuconfig is not doing very godo job.. i'll try to add that option manually.. it asks about IEEE802154_6LOWPAN11:44
kyakafter i added # CONFIG_IEEE802154_6LOWPAN is not set to target/linux/xburst/qi_lb60/config-3.3, everything works smooth11:48
kyaki'm reluctant to commit this change before you have a look.. not sure if you observe this problem on your side11:49
xiangfukyak, please commit. this option should take care by package/kernel/modules/wpan.mk11:54
qi-bot[commit] kyak: unset CONFIG_IEEE802154_6LOWPAN (master) http://qi-hw.com/p/openwrt-xburst/0c9426f11:55
paul_boddieAre Gtk+ and Qt actively maintained in OpenWrt? I can't say that I know how to do the git-related magic to pull in updates within the openwrt-nanonote build environment, but I didn't see much sign of activity on the various OpenWrt sites for those packages.12:08
xiangfukyak, let's wait the release build and test. 12:09
xiangfupaul_boddie, the gtk/qt is under 'svn://svn.openwrt.org/openwrt/feeds/xorg'12:11
xiangfumirko is maintain the qt. because I saw he is always try to fix qt build etc.12:12
paul_boddieI can see that here: https://dev.openwrt.org/browser/feeds/xorg/lib/qt412:14
paul_boddieI tried to update gtk, but I got bogged down in the various rearchitecturing changes that project made as they moved towards 3.0.12:14
paul_boddieUnless there's another repository, it seems to have stalled: https://dev.openwrt.org/browser/feeds/xorg/lib/gtk212:15
paul_boddieIf I could perform magic and make lots of time, I'd try and do a Debian-based equivalent software image, if only because of the active maintenance of such things in Debian and the use of things like glibc/eglibc which make some things easier.12:17
paul_boddieFiguring out what the gtk maintainers were thinking and then patching their build systems is hard work!12:17
xiangfuyes. agree12:20
paul_boddieMaybe I can learn something from this... Loading a kernel module from a file descriptor: http://lwn.net/Articles/519009/12:23
kyakpaul_boddie: don't bother with gtk update, since it doesn't support DIrectFB12:31
kyakthe release we are usign now is probably the last one where DIrectFB works12:31
paul_boddiekyak: I'm delegating all such matters to Debian at the moment, although I'm also not using gtk actively, anyway.12:31
kyakdo you run X?12:32
paul_boddieNo, just framebuffer stuff.12:52
paul_boddieI wanted pygame support with numpy, but I may change my mind again at some point. But I doubt that X is likely to be an option.12:53
paul_boddieIt's a shame Python uses 10MB of the RAM. Maybe it should go on a diet.12:57
kyakif debian gtk packages run fine on framebuffer, perhaps we should have a look how it's done13:12
kyakin DirectFB that is13:12
kyaki once updated gtk2 from 2.17.0 (currently in Openwrt) to 2.24.4 only to see that DirectFB is broken13:14
kyaki then read at their ML or somewhere else that it's not maintained anymore13:14
kyak..and then it is planned to drop it completely from gtk313:15
kyaknot planned, already dropped13:16
kyakeverything is getting fat nowadays and needs a diet :)13:16
kyakbetter stick with qt4.. its support for DirectFB is far more superior13:23
kyakcan even switch keyboard layouts13:24
kyakand more apps (at least in qi-packages)13:24
kyakbtw, qt4 builds as i speak.. fingers crossed (maybe it was an intermittent problem on buildhost)13:26
paul_boddieIt feels like all these projects are going backwards.13:39
kyakif they continue going backwards they will end up running fine on a PC with 32 Mb RAM :)13:44
paul_boddieSadly, they don't seem to go backwards in the resource usage department. I suppose the reason for not supporting the framebuffer any more is that we all have amazing 3D hardware now, or something.13:58
qi-bot /msg xiangfu test14:03
qi-bot/msg xiangfu tes14:04
kyak'msg' implied :)14:52
whitequarkpaul_boddie: it actually makes sens14:57
whitequarkwell, take for example wayland. it is a given fact that every desktop in last 10 years or so has at least Intel card, and that card is capable of compositing.14:57
whitequarkit is also a given fact that every Android smartphone since 3.0 has a mandatory GPU.14:58
whitequarkthis comprises the overwhelming majority of systems where graphical Linux should run.14:58
whitequarkon the other hand, what Ubuntu does with Unity, well, just sucks14:59
whitequarkthey are seemingly uncapable of programming14:59
paul_boddieWhat doesn't make sense is the churn in the software stack. That's how we end up with desktop environments that are less functional than the ones they "replaced", and only after huge amounts of extra work and disruption.14:59
whitequarkyeah, let's stay with 1987's crap14:59
whitequarkbits do not rot; true. unfortunately, architecture of X11 has like nothing to do with the modern desktop. it's an obsolete abstraction.15:00
whitequarktake even network transparency. both gtk and qt in a network-transparent mode basically transfer pixmaps, which means that even VNC is more efficient, not even talking about a wayland network transport module (yet to be developed)15:01
whitequarkand per usage department... people like fast software, and so time-memory tradeoffs are almost always solved in the favor of time.15:02
whitequarkwhich unfortunately means that you spend limited resource (memory) instead of unlimited (cpu cycles)15:02
whitequarkpaul_boddie: and if you're speaking about gtk3/gnome3, well, it was the reason I've switched to KDE.15:05
paul_boddieNot everything in 1987 was crap, though. ;-)15:06
whitequarkpaul_boddie: what wasn't? If we are talking about software.15:07
whitequarkI don't really see any piece of software from 1987 or its descendant which I would use except for compatibility15:07
whitequarkexcept, maybe, games. nethack is pretty cool.15:07
paul_boddieInteresting question. I thought we were talking about hardware, but I'm pretty sure some essential software from 1987 is still around and isn't crap.15:08
whitequarkwell, 1987 hw wasn't exactly bad per se, it was just not very developed15:10
whitequarkjust as latest steam engines weren't crap15:10
whitequarkemphasis on "latest". hardware went a very long way from those times, software is still commonly written in C with mostly same errors and patterns.15:11
larsceven C was crap back in 1987, at least by todays standards ;)15:20
kyakif you look back, you might say, that, yeah, SW from 1987 is crap. But it wasn't crap back then. I don't like it that i feel like crap with 1Gb RAM, even running minimalistic Linux15:34
kyakso the difference is that the today's SW is crap right now15:35
kyakwhile you can only call the SW from 1987 crap after 20 years15:35
wpwraki daresay that sw from 1987 should be impressibly fast on today's hardware. around 1987 .. i think i had an ~8 MHz 8086-based PC with 640 kB of RAM (Amstrad PC-1512). floppy disks as mass storage. all that old sw would still run on my modern (just a few ywars old) PC, at several hundred times the speed. my floppy collection would comfortably fit in a RAM disk.15:40
mthwpwrak: there are a lot of good games from that era, but we emulate the old hardware rather than port the games16:36
mtheh, I meant whitequark16:37
mthshould have typed two letters before tab...16:37
mthporting wouldn't really be an option anyway, since most of the source code is proprietary, probably a lot of it is lost and a big portion was written in assembly rather than C16:38
mthabout X11: I ran a remote desktop for a few years at work, where I had to use Windows for company-issued applications but did all development in Linux16:41
mthbut I used NX rather than plain X11 because it performed better with KDE316:41
mthremote X works very well with applications from 15 years ago, but not so well with GTK/Qt since they introduced theming and gradients etc16:42
whitequarkindeed, and people want theming and gradients16:42
whitequarkhonestly, I would _not_ want to work on a 15-year-old desktops. it wasn't minimalistic because that's better, it was minimalistic because hardware was stupid.16:43
whitequark(apart from the fact that my main application runs in jvm and requies 1g+ to just start. it's a server one through, and that is well justified.)16:43
whitequark*15-year-old apps for plain X, if you'd like.16:44
whitequarkwpwrak: it's indeed impressively fast, but is also very significantly featureless. e.g. C compilers.16:44
whitequarkyou still have tcc which would perform amazingly on a 25-year-old hardware16:45
whitequarkbut you also have "slow" and "bloated" LLVM which performs optimization better than humans do.16:45
whitequarkand, well, there is almost no problem fitting a modern _equivalent_ of 15-year-old software on a floppy disk16:46
whitequarkthe problem is that people don't want an equivalent of black-and-white windows and dumb compilers and naive memory managers, they want more16:46
mthI still want to write a Z80 backend for LLVM one day16:47
wpwrakhmm. i use fvwm as window manager. that one's about 18 years old, more than the 15 you find unacceptable. and it still serves me very well.16:47
mththere are still people writing games for Z80 machines, but the C compilers they use are very poor at optimization16:47
mthso they have to do all performance critical parts in asm16:47
mthoh wow, I have to test that16:48
whitequarkwpwrak: does it have antialiased fonts, for example?16:48
whitequarkto be precise, Xft fonts.16:48
wpwrakdunno. doesn't matter anyway. it's a window manager, not an e-book reader.16:49
whitequarkit's a perfect example of how X11 does not work. my notebook has a DPI of 170, and plain X fonts just don't work with it.16:49
whitequarkif you cannot read a fucking window title, it does matter a lot.16:49
whitequarkI'm using i3wm, for that matter, and it is nowhere like bloated. I can't stand plasma.16:50
wpwrakyou mean 170 dpi is too low for your needs ?16:50
whitequarkwpwrak: why is it too low? it's near perfect16:50
wpwrakyou're saying that the low resolution forces you to use fonts that have less than, say, 5x7 pixels16:51
wpwrakbecause at 5x7 and more, you don't need anti-aliasing16:51
whitequarksorry, what? it's _high_ resolution. your monitor probably has 95 dpi or so.16:52
whitequarkold X font system simply won't draw letters which are big enough16:52
whitequarkapart from the fact that it doesn't know how to draw truetype fonts at all, and pixelated fonts aren't good.16:53
whitequarkI'm not talking about subpixel antialiasing (which I hate)16:53
whitequarkjust the usual grayscale one16:53
wpwrakmy standard text font is 6x10, unaliased. it's very readable at 100 dpi.16:53
whitequarkyour vision is probably much better than mine then.16:53
mtheh, I prefer anti-aliasing on large font sizes, not on small ones16:54
whitequarkmth: I too16:54
whitequarkhttp://i.imgur.com/9qQqK.png < a screenshot16:54
mthreally small fonts have to be hand-optimized to be readable16:54
whitequarkmth: on my DPI I had to turn off hinting16:54
whitequarkit was making fonts significantly worse16:54
whitequarksrsly, once people see how do fonts look like on my display, they start saving money for the same notebook like I have.16:55
whitequarkand I mean that literally. well, at least in two cases.16:56
wpwrak(vision) hmm, probably not. when wearing lenses, i'm having trouble to see fonts of that kind of size (6x10 or even 7x14) on my 211 dpi laptop. the joy of getting old ...16:56
whitequarkto be honest I've no idea how big my letters are in terms of pixels16:57
whitequarkit's 10pt16:58
wpwrakif that screenshot is your normal environment, then they must be some 50 pixels tall. useful if you have very long arms, 10 m or so ;-)16:58
whitequarkwpwrak: indeed it is, let me get a photo of me working then16:59
mthat least KDE understands that DPI is implied by the combination of screen size and resolution and is not a setting17:01
whitequarkmth: actually, I had to choose it as a setting in KDE17:01
mthreally? that's a regression then17:01
whitequarkmight be. non-native resolutions on LCD displays are pointless anyway17:01
mthah, there is a "force fonts DPI" setting, but it's disabled on my PC17:03
kyakwhitequark: what's your notebook anyway?17:03
mthI can imagine it's useful if you have bad eyesight and want larger fonts from web pages17:04
mthbut in theory it shouldn't be necessary for normal use17:04
whitequarkwpwrak: http://imgur.com/k38Nr should give you an idea of how it looks in real life17:04
whitequarkkyak: asus ux32vd. highly recommend as a linux machine for work. i7, discrete gpu, up to 10Gb RAM, very good quality.17:05
whitequarkmth: Chrome ignores it anyway, I had to set default scaling to 125%17:05
mthbut Chrome uses GTK, right? I think GTK does see DPI as a setting, which is plain wrong17:06
whitequarkmth: it's an open bug in Chrom[ium]17:06
whitequarkor rather in webkit17:07
kyakwhitequark: it's a good time, right now i'm looking for my home laptop replacement :)17:07
whitequarkmth: the point is, for two decades web designers thought that dpi==96.17:07
whitequarkand now if you just change the dpi in webkit, half of web breaks17:07
mthyeah, I still have to tell people who write CSS that they should be using points rather than pixels except when dealing with bitmaps17:08
whitequarkbitmaps, ewww. blurred web is also a norm for me nowadays :/17:08
mthwell, if you have something like a screenshot, a bitmap is unavoidable17:08
whitequarkmth: for UI17:08
whitequarke.g. gradients or buttons17:09
whitequarkespecially icons on buttons17:09
whitequarkso awful17:09
mthand unfortunately IE was very late with SVG support, so if you want fancy icons bitmaps are still the only real option17:09
kyakwhitequark: oh, 13.3" and Full HD? i currently have 15.6" and Full HD, and everything is pretty tiny (this is my WIndows machine at work)17:09
kyaki was looking for something 17" :)17:09
whitequarkkyak: yeah, it's 13.3", Full HD _and_ IPS!17:09
kyakwhat's IPS?17:10
whitequarkin-plane switching17:10
kyakuh. let me google it for me :)17:10
whitequarka technique of making LCD displays which makes white look like white and black like black17:10
whitequarkand not like some dim, boring crap17:10
mthand it's got a much better viewing angle than TN panels do17:10
whitequarkyep, 178 of 180 degrees17:10
whitequarki.e. any way you could want to look at it.17:11
kyakyeah, i'm thinkinh about it17:11
mthI got an S-PVA monitor for my desktop, that also has a good viewing angle17:11
kyaki was not considering anything below 15", so this laptop didn't catchmy attention..17:11
mthI really dislike it when colors change if you tilt your head a bit17:11
whitequarkmth: especially if the most convenient looking angle does not match with the optimal LCD viewing angle17:12
whitequarkannoying like hell17:12
mthwith a laptop that often happens, with a desktop it's not so common17:12
mthbut a desktop monitor is larger, so you are looking at sharper angles more often17:13
mthput an even color on the desktop background on a large TN panel and you'll see a gradient17:13
whitequarkwell I don't generally collect posessions of significant size. I like it if I can just pack all my stuff in a single backpack and go somewhere. so... no desktops as you can guess17:14
mthI'm pretty much the opposite, I only travel if I really want to be in some other place17:14
whitequarkmth: I don't generally travel much17:15
whitequarkrather the opposite17:15
whitequarkI just like that I can do that.17:15
mthah ok17:15
whitequarkreduces amount of cruft in the place where you live, forces you to optimize consumption17:15
mthI don't like to throw away stuff that still works, so I've got quite a lot of old hardware around17:18
wpwrakwhitequark: seems excessively huge. but well, maybe when i hit 60, i'll appreciate such sizes too... :)17:18
whitequarkmth: I don't either, I give it away to those who need it17:19
wpwrakbtw, white on black may help. allows the eye to use a smaller aperture, which increases the field of vision17:19
mthit's not huge at 170 dpi though17:20
whitequarkwpwrak: hm. seems pretty normal to me.17:20
whitequarknot really significantly bigger than on my previous notebook with an ordinary display17:20
wpwrakthat's a good trick to know when suffering age-related farsightedness17:20
whitequarkwpwrak: (white on black) I hate that combination. It always happens that I open the lid at night and, ow, my eyes are in pain17:21
wpwrak(not specifically for displays but for any reading/viewing situation)17:21
mthwhitequark: I give away my old PCs, but I like to keep old game consoles around in case I want to play old games again17:21
wpwrakwhitequark: that's what you get for trying to work before the hangover has subsided ;-)17:21
whitequarkwpwrak: hahaha17:27
kyakwhitequark: i'm looking more into this beast: http://market.yandex.ru/model.xml?modelid=7795517 :)17:37
kristianpaulthe only think i look when i buy a computer is display actually, if it reads ok no much bright and high resolution in small package is a way to go for me17:45
kyakmirko: a bunch of qt4 packages result in the following error: Package qt4-drivers-gfx-directfb is missing dependencies for the following libraries: libQtGui.so.4 libQtNetwork.so.418:41
kyakapart from qt4-drivers-gfx-directfb these are *mouse drivers and qt4-mysql (missing libmysql_r)18:41
kyakadding +qt4-gui and +qt4-network in DEPENDS for these packages yeilds strange results - these entries dissappear from .config18:43
kyakadding +PACKAGE_qt4-mysql:libmysqlclient-r to qt4-mysql DEPENDS solved the problem for qt4-mysql.. But for other packages, the situation seems different18:44
kyaki guess there is some cyclic dependency with qt4-gui and qt4-network18:44
kyakmirko: running with the following patch now: https://gist.github.com/3874950 . Hope it helps, trial-and-error iterations over qt4 take so long19:33
FrankBluesAck, wrong window, heh20:08
qi-bot[commit] Marcos Paulo de Souza: media/radio/radio-rda5807.c: Use devm_* when allocating memory (jz-3.6) http://qi-hw.com/p/qi-kernel/dbd96db22:52
qi-bot[commit] Marcos Paulo de Souza: media/radio/radio-rda5807: Use module_i2c_driver instead of module_{init|exit} (jz-3.6) http://qi-hw.com/p/qi-kernel/a96c58422:52
qi-bot[commit] Marcos Paulo de Souza: media/radio/radio-rda5807.c: Wait for seek complete before return (jz-3.6) http://qi-hw.com/p/qi-kernel/7b4d42722:52
--- Fri Oct 12 201200:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!