Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2016-01-10

00:02:06 Quit krnlyng (Ping timeout: 250 seconds)
00:32:42 Quit petur (Remote host closed the connection)
00:33:22 Join krnlyng [0] (~liar@77.117.8.36.wireless.dyn.drei.com)
00:35:07***Saving seen data "./dancer.seen"
00:39:12*[Saint] wonders if the Xduoo guys are just marketing idiots like everyone else or if there really is a 128GB hard limit on addressable SD size.
00:39:51[Saint]I realize it's hard to do with a CNC machined case, but, those dust traps...I mean SD slots, are really awful.
00:41:25[Saint]all the text on their site is fucking jpgs.
00:41:28[Saint]lol
00:44:02[Saint]There's really something fundamentally wrong with the player though, or they are vastly underestimating the runtime.
00:44:29[Saint]1500mAh battery, ~8h runtime. According to them.
00:45:40[Saint]perhaps they don't do any clockswitching.
00:47:39 Join Markmaster [0] (~Markmaste@173.192.207.18)
00:47:39 Quit Markmaster (Client Quit)
00:48:49 Quit ender` (Quit: If Java had true garbage collection, most programs would delete themselves upon execution. -- Robert Sewell)
00:51:09 Quit Markmas__ (Ping timeout: 264 seconds)
00:51:28 Quit rasher (Changing host)
00:51:28 Join rasher [0] (~rasher@rockbox/developer/rasher)
00:53:10pamaury[Saint]: what do you mean by 128GB limit ?
00:53:51[Saint]It's probably a marketing blunder, like it usually is, but they tout "up to 256GB" from 128GB x2 SD slots.
00:54:12[Saint]But the company is just weird enough that I'm not quite prepared to believe it's not a real hard limit.
00:55:59pamauryI guess it's just that 128GB is the current limit of one SD card, so with 2 slots, you get twice the maximum size ?
00:56:25[Saint]but it's not, though. but, yeah, the marketing team is probably just idiots.
00:57:05[Saint]128GB hasn't been the upper bound for quite a while now.
01:00
01:06:09pamaury256GB micro-sd cards are not that common
01:07:42pamauryand even then, if you have two 256GB slot, that makes it 512GB which you can't reach with current microsd cards (unless you are ready to pay an insane price)
01:07:55[Saint]200GB.
01:08:01[Saint]256GB are vaporware.
01:08:09[Saint]They "exist", but, they...don't.
01:08:50[Saint]either way, I expect to see the max capacity listed as 2TB of addressable space for any non-idiot company.
01:09:02[Saint]Android OEMs clicked onto this fuckery years ago.
01:09:52[Saint]These guys are special snowflakes, so they get to say /4TB/, why would you not use that to you're advantage?
01:10:18[Saint]You're already listing audio bit throughput that's entirely meaningless to the consumer.
01:10:25[Saint]WHy not more big numbers? :)
01:11:00pamauryThey are aiming at audiophile, those numbers may be attractive to those people ?
01:11:34[Saint]I'm not sure if you're helping to make your point, or mine.
01:11:37pamauryanyway, I still don't see the point, how is it bad to market about something realistic (2x128GB) rather something possible but super far streched (2x2TB) ?
01:11:59[Saint]because one is an outright fucking lie.
01:12:04[Saint]and the other is a truth?
01:12:05pamauryI'm not making any point ;) you seem to have a problem with them, I don't care ^^
01:12:30[Saint]I have a problem with people who don't understand the technical abilities of their product making marketing material.
01:12:35[Saint]Not Xduoo directly.
01:13:11pamauryI mean common, did you ever see a PC manufacturer say "up to 128XiB of storage" just because it can 2^128 sectors of 512 bytes ? (just making numbers)
01:13:13[Saint]This "up to N GB" crap is rife in all kinds of communities, but many OEMs in the Android space kissed that game goodbye quite some time ago.
01:13:38[Saint]Most Android devices list "up to 2TB" as the upper bound for SD now, as per spec.
01:14:34[Saint]Because it's disingenuous to say otherwise, and it attracts idiots.
01:14:51[Saint]I wonder how many support requests they've handled asking if it supports 200GB cards.
01:14:59[Saint]A lot, I'd wager.
01:17:45 Join girafe [0] (~girafe@AGrenoble-651-1-511-220.w82-122.abo.wanadoo.fr)
01:18:24pamauryok I see where you are going, I guess you have a point, Perhaps the idiot marketer didn't speak to the half-competent engineer and came up with those numbers by himself :-p
01:24:18 Quit lebellium (Quit: ChatZilla 0.9.92 [Firefox 44.0/20160107144911])
01:51:59 Quit bertrik (Remote host closed the connection)
01:59:45 Join tux00 [0] (4da48d93@gateway/web/freenode/ip.77.164.141.147)
01:59:52tux00hy all
02:00
02:00:27tux00some one here ?
02:02:22 Part tux00
02:05:02__builtinhi
02:06:38 Quit pamaury (Ping timeout: 272 seconds)
02:35:08***Saving seen data "./dancer.seen"
02:48:15 Quit girafe (Read error: Connection reset by peer)
03:00
03:17:20 Quit krabador (Ping timeout: 256 seconds)
03:30:47 Join ZincAlloy1 [0] (~Adium@p5B2FC3FE.dip0.t-ipconnect.de)
03:34:02 Quit ZincAlloy (Ping timeout: 272 seconds)
03:40:46 Quit ZincAlloy1 (Quit: Leaving.)
04:00
04:16:08 Join rela [0] (~x@pdpc/supporter/active/rela)
04:35:11***Saving seen data "./dancer.seen"
05:00
05:22:34 Quit TheSeven (Ping timeout: 240 seconds)
05:24:00 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven)
05:46:15 Join PurlingNayuki [0] (~Thunderbi@124.127.70.80)
06:00
06:35:14***Saving seen data "./dancer.seen"
06:50:17 Quit Strife89 (Read error: Connection reset by peer)
07:00
07:12:08 Join Strife89 [0] (~Strife89@2600:1005:b06d:45c:5817:a672:96d2:1fee)
08:00
08:26:40 Quit rela (Quit: Leaving)
08:26:55 Join rela [0] (~x@pdpc/supporter/active/rela)
08:35:18***Saving seen data "./dancer.seen"
10:00
10:10:29 Quit krnlyng (Ping timeout: 260 seconds)
10:22:06 Quit sparetire_ (Quit: sparetire_)
10:29:35 Join xorly [0] (~xorly@ip-86-49-15-121.net.upcbroadband.cz)
10:30:18 Join krnlyng [0] (~liar@178.114.27.155.wireless.dyn.drei.com)
10:34:50 Join bertrik [0] (~quassel@rockbox/developer/bertrik)
10:35:22***Saving seen data "./dancer.seen"
10:55:37 Join ender` [0] (krneki@foo.eternallybored.org)
11:00
11:33:28 Join petur [0] (~petur@rockbox/developer/petur)
11:36:11 Join krabador [0] (~krabador@unaffiliated/krabador)
11:45:10 Quit krnlyng (Ping timeout: 264 seconds)
11:56:29 Quit JanC (Read error: Connection reset by peer)
11:58:08 Join JanC [0] (~janc@lugwv/member/JanC)
11:58:41 Join lebellium [0] (~chatzilla@89-93-179-187.hfc.dyn.abo.bbox.fr)
12:00
12:13:56 Join krnlyng [0] (~liar@178.114.125.175.wireless.dyn.drei.com)
12:35:26***Saving seen data "./dancer.seen"
13:00
13:06:16 Nick suYin`OFF is now known as suYin (mysuyin@server2.shellfire.net)
13:47:10 Join krnlyng_ [0] (~liar@77.116.13.16.wireless.dyn.drei.com)
13:48:12 Quit krnlyng (Ping timeout: 276 seconds)
13:49:15 Nick krnlyng_ is now known as krnlyng (~liar@77.116.13.16.wireless.dyn.drei.com)
14:00
14:12:04 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
14:28:14 Quit Poodlemastah_ (Ping timeout: 260 seconds)
14:35:30***Saving seen data "./dancer.seen"
14:52:40 Quit krnlyng (Quit: huiiiiii)
14:53:52 Join krnlyng [0] (~liar@83.175.90.24)
15:00
15:06:20 Quit krabador (Remote host closed the connection)
15:30:48 Join ZincAlloy [0] (~Adium@p5B2FC3FE.dip0.t-ipconnect.de)
15:46:22 Join Poodlemastah [0] (~Poodlemas@109-124-181-219.customer.t3.se)
15:48:08 Join Strife89|AndChat [0] (~Strife89@adsl-98-80-199-115.mcn.bellsouth.net)
15:51:33 Quit Strife89 (Ping timeout: 250 seconds)
15:57:12 Join Strife89 [0] (~quassel@adsl-98-80-199-115.mcn.bellsouth.net)
16:00
16:06:45 Join sparetire_ [0] (~sparetire@unaffiliated/sparetire)
16:23:33 Join Steife1989 [0] (~Strife89@2600:1005:b06d:45c:1a86:3bd:6659:fee2)
16:26:09 Quit Strife89|AndChat (Ping timeout: 256 seconds)
16:34:19 Quit PurlingNayuki (Ping timeout: 255 seconds)
16:35:31***Saving seen data "./dancer.seen"
16:41:22 Quit bluebrother (Disconnected by services)
16:41:27 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother)
16:44:34 Quit Steife1989 (Ping timeout: 240 seconds)
17:00
17:03:16 Quit krnlyng (Quit: huiiiiii)
17:20:09 Join krnlyng [0] (~liar@77.116.13.16.wireless.dyn.drei.com)
17:32:54 Quit JanC (Ping timeout: 240 seconds)
17:46:46 Join JanC [0] (~janc@lugwv/member/JanC)
18:00
18:17:52 Join PurlingNayuki [0] (~Thunderbi@124.127.70.80)
18:35:35***Saving seen data "./dancer.seen"
18:37:55 Join girafe [0] (~girafe@AGrenoble-651-1-511-220.w82-122.abo.wanadoo.fr)
18:54:25pamauryah ingenic, so apparently they have two timer blocks, only one is documented but for some reason they made changes to the other one between JZ4760 and JZ4760B, of course none of this is listed in the document which gives the difference between the two...
18:57:10 Quit PurlingNayuki (Ping timeout: 264 seconds)
19:00
19:05:54 Quit krnlyng (Ping timeout: 240 seconds)
19:09:37pamauryalso they suck at register naming convention
19:19:11 Join krnlyng [0] (~liar@178.114.124.18.wireless.dyn.drei.com)
19:26:17pamauryok, so who is the engineer that decided that all registers name should be of the BLOCK_REG but then decided that all registers names should begin with a few letters to identifier the block ? Thus leading to names like BLOCK_BLOCKREG ?
20:00
20:00:08 Quit megal0maniac (Ping timeout: 260 seconds)
20:05:43 Join megal0maniac [0] (~megal0man@unaffiliated/megal0maniac)
20:15:01 Quit krnlyng (Ping timeout: 246 seconds)
20:21:19 Quit pamaury (Read error: Connection reset by peer)
20:22:27 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
20:27:31 Join krnlyng [0] (~liar@178.112.203.240.wireless.dyn.drei.com)
20:35:36***Saving seen data "./dancer.seen"
21:00
21:07:18*[Saint] found ENUM_ENUM_ENUM_ENUM the other day.
21:07:39[Saint](re: fucking bonkers naming schema)
21:22:33 Quit krnlyng (Ping timeout: 276 seconds)
21:36:11 Join krnlyng [0] (~liar@77.117.66.179.wireless.dyn.drei.com)
21:49:02pamauryyay, I finally have a first version of jz4760b registers \o/
21:49:33pamauryI still have to check that againts the manual, there were so many errors in those headers
21:50:11pamaurynot to mention a few sneaky difference between jz4760 and jz4760b, I hope this won't be too much of an issue
21:52:33 Join quaz0r [0] (quaz@c-67-183-243-24.hsd1.wa.comcast.net)
22:00
22:12:33 Quit rela (Ping timeout: 240 seconds)
22:35:38***Saving seen data "./dancer.seen"
22:42:54 Quit krnlyng (Ping timeout: 272 seconds)
22:44:59[Saint]vlcn: did you die?
22:45:13[Saint]vlcn: or did I feed you enough to get you up and running?
22:47:23 Join krnlyng [0] (~liar@178.112.150.212.wireless.dyn.drei.com)
22:48:41 Quit shamus (Quit: chaos reigns within reflect repent and reboot order shall return)
22:54:10 Quit Poodlemastah (Read error: Connection reset by peer)
22:54:51 Quit pamaury (Remote host closed the connection)
22:55:29 Join wodz [0] (~wodz@89-75-106-221.dynamic.chello.pl)
22:55:56 Join Poodlemastah [0] (~Poodlemas@109-124-181-219.customer.t3.se)
22:56:33wodzpamaury: (log) Whoa, I see resumed tinkering with DAPs :-)
22:59:04 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
22:59:28 Join PurlingNayuki [0] (~Thunderbi@124.127.151.6)
23:00
23:00:21pamaurywodz: yeah I'm trying to put some of free time on tis
23:00:23pamaury*this
23:00:39pamauryI've actually spend quite some time on this register map because of those crappy headers
23:00:50wodzgood to see something going
23:00:55 Nick suYin is now known as suYin`OFF (mysuyin@server2.shellfire.net)
23:01:07pamaurynow I understand why the headers come with all those functions
23:02:13wodzwhat you mean?
23:02:50pamaurythe headers are so inconsistent that using the define directly is a challenge. So they just define a lot of function to work with them
23:03:36wodzah, that
23:04:22pamauryI'll push it to gerrit after doing some more checks on it. Then I'll try to play with the lcd on the fiio X1
23:06:04pamaurywodz: by the way did you see that I updated the hwstub library rework to gerrit ?
23:06:21wodzYes, but I didn't had time to look at this
23:08:18pamaurysure no problem
23:10:07wodzhow complete this rework is now?
23:10:36pamauryit is missing the network part
23:11:38pamaurywhich should be easy to add now. Also I initially thought about writing a C->C++ wrapper for the tools but now I'm thinking about porting the tools to it directly, it's not a major change anyway
23:11:52wodzok, so is this drop-in replacement for what is in HEAD
23:11:54wodz?
23:13:05pamauryyeah that's the idea, except for the fact that many of the tools don't compile anymore so I need to port them. I hope to finish this quickly
23:18:51 Join sasha86 [0] (~gremlin@87.116.141.30)
23:23:07 Quit preglow (Remote host closed the connection)
23:26:37 Part sasha86 ("Leaving")
23:32:37 Quit wodz (Quit: Leaving)
23:35:13 Quit bertrik (Remote host closed the connection)
23:35:37 Join preglow [0] (~thomj@2001:840:4243:3::101)
23:52:53 Quit lebellium (Quit: ChatZilla 0.9.92 [Firefox 44.0/20160107144911])
23:56:41 Quit petur (Quit: Leaving)
23:58:20 Quit krnlyng (Ping timeout: 256 seconds)

Previous day | Next day