<naobsd>
about tsadc, what I read is /sys/devices/*.tsadc/*input on RK 3.10 kernel on RK3288
FreezingCold has quit [Ping timeout: 264 seconds]
<naobsd>
now I have admins right of here/wiki/maillist/etc,
<naobsd>
everyone can blame me about progress of linux-rockchip thing officially :)
<ganbold_>
naobsd: you are doing it voluntarily, so noone can demand anything from you what they want :)
<naobsd>
ganbold_: it's not *BSD community, sometimes I heard like "you should contribute it more/quickly"
<naobsd>
I'm sure that messages posted on IRC will be missing soon
<naobsd>
I should
<naobsd>
I should write wiki, I want write wiki
<naobsd>
but some amount people say "you should write wiki" before say "thanks!"
<naobsd>
I shouldn't use here for 1st place to answer question ;)
FreezingCold has joined #linux-rockchip
dujw has joined #linux-rockchip
levs has joined #linux-rockchip
levs has quit [Client Quit]
dujw has quit [Ping timeout: 272 seconds]
dujw has joined #linux-rockchip
aaaaaaaaaaa is now known as Adrian
dujw is now known as zslevin{away}
FightingCat has joined #linux-rockchip
naobsd has quit [Quit: Page closed]
FreezingCold has quit [Ping timeout: 260 seconds]
GriefNorth has joined #linux-rockchip
nobody_ has joined #linux-rockchip
nobody_ has left #linux-rockchip [#linux-rockchip]
dlezcano has quit [Ping timeout: 245 seconds]
akaizen_ has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
hipboi has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi has quit [Ping timeout: 246 seconds]
hipboi has joined #linux-rockchip
GriefNorth has quit [Quit: WeeChat 1.0]
viric has quit [Ping timeout: 240 seconds]
viric has joined #linux-rockchip
<rperier>
hi all
<rperier>
my proposal sent to devicetree ML did not convinced people apparently... (about system-power-controller)
GriefNorth has joined #linux-rockchip
wildea01 has joined #linux-rockchip
<mmind00>
rperier: normally the paradigm is to let "code speak" I think
<mmind00>
i.e. implement it in one driver [with your rationale being woven into the commit message] and maybe even add support for the new properties to the other drivers using vendor specific things
<mmind00>
aka make tps65910 support both the "ti,system-power-controller" and the new generic "system-power-controller", same for the rk808 etc
<mmind00>
maybe another important thing ... you've written this yesterday 4pm, so generally you shouldn't expect a response less than 24 hours later ...
<karlp>
now just need to get more info on what boots what in what order and keep expanding...
<rperier>
mmind00: ah jet lag... you're right
<rperier>
mmind00: I need to investigate why I loose tcp packets with emac_rockchip first
<rperier>
it has probably something to do with speed negociation or macref clock frequency.
<rperier>
(I mean comparated to emac_arc which works just fine)
<rperier>
yeah I will propose an implementation, it will give context about what I have in mind (for system-power-controller)
<mmind00>
rperier: to check the clock, try to mount debugfs and look at $debug-mount-point/clk/clk_summary
<mmind00>
macref should decend from the dpll at exactly 50MHz
<mmind00>
but if I remember correctly, if the clock does not have exactly 50MHz, you don't get any packets at all
<rperier>
mhhhh interesting, I will take a look to it, this evening
naobsd has joined #linux-rockchip
<naobsd>
karlp: thank you for updating wiki
<karlp>
thanks for the initial info.
<karlp>
I can always hack the wiki, but you'll need to answer my questions :)
<karlp>
so, I still don't know how you make the magic header portion :)
<naobsd>
I just got it from SD card after official SD boot card creating tool(I forgot name)
<naobsd>
...after running...
<karlp>
I know the temptation to answer a question on irc directly :) I've done that myself,
<naobsd>
oh
<naobsd>
sorry
<naobsd>
ask naobsd -> ask naobsd to write wiki
<karlp>
the reason I hadn't written any more stuff earlier was that I _hadn't_ fully understood/confirmed what you'd said :)
<karlp>
don't sweat it, I'm not complaining, you were just asleep when I was on that part :)
<naobsd>
I think confirmation should be done by others before writing wiki
<naobsd>
IRC is the place for posting random message
<naobsd>
wiki is for confirmed/arranged/summaried info
<karlp>
well, we'll just keep improving over time I'm not concerned.
<naobsd>
(it's just my personal image)
<karlp>
anyway, back to real day job work for a while :)
<naobsd>
people who read wiki just believe it w/o confirmation
<naobsd>
I see
<naobsd>
wiki is not the blog(I think), even if there are questions, no heed to write words like "(someone) says ..." "I have no idea", just put mark like (need more information) (need confirmation) (tbd) etc
<karlp>
I agree, but sometimes it's better to have one place that says, "here's what people have said" rather than not saying anything at all, and making people try and find what other people have said.
<karlp>
but yeah, I'm trying to just copy the internet onto the wiki, that's clearly never goign to work :)
<naobsd>
well probably what I wanted to say is
<naobsd>
curation?
<naobsd>
my english vocabulary is poor :(
<naobsd>
not scrapbook
<naobsd>
not log of day-by-day trial&error
<karlp>
I understand you :)
<karlp>
my blog gets some brain dump bits, as more bits become clearer I'm trying to get them written upbetter,
<karlp>
and occasionally I will be poking people for answers to clarify things.
<karlp>
I'm quite used to there being people who know things, but not much written down, irc interviews then me reformatting them into wikis is something I've done before and will do again :)
bengal has joined #linux-rockchip
bengal has quit [Ping timeout: 264 seconds]
<naobsd>
how many RK3288 is required to make smart hot plate :)
GriefNorth has quit [Quit: WeeChat 1.0]
naobsd has quit [Quit: Page closed]
hramrach has quit [Ping timeout: 264 seconds]
hramrach has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
<rperier>
mmind00: there are still development to do on mainline for RK3288 ? (that's for future works, when I wil buy a firefly rk3288)
<rperier>
I mean, they are apparently a lot of progress for the rk3288, the nand seems to work, a lot of I/O too.
<mmind00>
rperier: nope nand doesn't work ... emmc does ;-)
JohnDoe_71Rus has joined #linux-rockchip
<rperier>
oh yeah it was emmc sorry
<mmind00>
for the other stuff, I cannot say how this will progress until then ... but I'd think the number of free "projects" on the rk3288 will be a lot lower than on rk3188 etc ... simply because everybody is focussing on the rk3288 right now
<mmind00>
there are things like the smartcard and gps controller, but even if the firefly does lead the pins to its headers, it will require wiring these up to some hardware
<karlp>
(for a tiny voice in the back of the room, I'd rather see 3066/3188 stuff before smartcard and gps peripherals of 3288)
<mmind00>
karlp: I share that thought ... rk3288 is "overrun" by people doing this as their main work ;-)
<rperier>
I see, so that's probably better to focus on RK3066 and RK3188 in this case (for mainline development and support, at least for now)
<rperier>
focus on boards/soc which require the most of support
<karlp>
mmind00: about dts, the arch/arm/boot/dts tree is monstrous already, and there's only one or two machines there at the moment, am I really meant to add a whole new dts for my minix device?
<karlp>
or will we at some point see dtsi files for the common "reference" designs?
<karlp>
my .dts only differes from the bqcurie in dropping the buttons at present, and changing the name.
<mmind00>
karlp: putting the reference design into an include that would be the long term plan
<karlp>
(it will have more eventually, the minix has an ethernet port, for starters)
<karlp>
ok, that's good, helps me understand the roadmap :)
<mmind00>
but initially I'd like to collect the common patterns first
<mmind00>
it's not a roadmap ... I only had the same thoughts in the past ;-)
GriefNorth has joined #linux-rockchip
akaizen_ has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
viric_ has joined #linux-rockchip
viric has quit [Ping timeout: 240 seconds]
viric_ is now known as viric
FightingCat has quit [Remote host closed the connection]
zslevin{away} has quit [Ping timeout: 240 seconds]
bengal has joined #linux-rockchip
bengal has quit [Ping timeout: 268 seconds]
wildea01 has quit [Quit: leaving]
ChiaSmurf has quit [Ping timeout: 260 seconds]
ChiaSmurf has joined #linux-rockchip
ChiaSmurf has quit [Ping timeout: 272 seconds]
nighty^ has quit [Quit: Disappears in a puff of smoke]