 boot the test images from usb?
<plars> ogra_: so I'll likely need to make similar changes to uboot that boots from the mmc on our rpi2
<ogra_> well. i was wrong the uboot change was in 0.15 already
<ogra_> when we dropped all txt files
<plars> ogra_: right, this problem is just affecting rpi2, nothing else
<ogra_> so between 8 and 9 there were only minor kernel adjustments
<plars> I'm gussing 187 for generic_armhf got the same kernel adjustments?
<plars> *guessing
<ogra_> no idea, i dont touch amd64 usually
<plars> ogra_: I'm not saying amd64
<ogra_> oh, generic_armhf, sorry, i misread
<ogra_> might be, i didnt look at BBB for a long time either
<plars> :)
<plars> something in those changes broke rpi2 for us
<ogra_> (last time for the uboot changes but they were far before that)
<plars> ogra_: bbb works fine
<plars> rpi2 is completely busted for the way we have to automate it though
<ogra_> well, both are identical on the uboot level
<ogra_> both dont use txt files anymore and require editing of uboot.env
<plars> so either we need some other options for automating (unlikely unless they release a rev of the board with better hardware) or we need to figure out what changed and roll it back
<ogra_> and both use the same kernel... with RPi having a set of extra HW patches on top
<plars> ogra_: I don't expect bbb to break here, we don't have to do this trick to make bbb boot
<plars> ogra_: bbb boots off the sd card, just as if you had flashed it, because we can boot a stable image off of emmc
<ogra_> http://people.canonical.com/~ogra/core-image-stats/20151002.changes thats the rootfs changes of 187
<plars> ogra_: rpi only has one place to boot from, so we have to resort to pushing the new image to usb - did anything with usb perhaps?
<ogra_> plars, yes, i know,
boot the test images from usb? 
 < plars > ogra _: so I'll likely necessitate to name similar changes to uboot that boots from the mmc on our rpi2 
 < ogra _ > well. i was improper the uboot change was in 0.15 already 
 < ogra _ > when we dropped all txt file 
 < plars > ogra _: right, this trouble is just affecting rpi2, nothing else 
 < ogra _ > so between 8 and 9 there were only minor kernel adaptation 
 < plars > I'm gussing 187 for generic_armhf got the same kernel adjustment? 
 < plars > * guessing 
 < ogra _ > no idea, i do nt touch amd64 usually 
 < plars > ogra _: I'm not saying amd64 
 < ogra _ > oh, generic_armhf, sorry, i misread 
 < ogra _ > might be, i did nt search at BBB for a long time either 
 < plars > :) 
 < plars > something in those changes break rpi2 for us 
 < ogra _ > (last time for the uboot changes but they were far before that) 
 < plars > ogra _: bbb works all right 
 < plars > rpi2 is completely break for the way we have to automate it though 
 < ogra _ > well, both are identical on the uboot grade 
 < ogra _ > both do nt use txt files anymore and require editing of uboot.env 
 < plars > so either we need some early option for automating (unlikely unless they release a rev of the board with better hardware) or we need to figure out what changed and wheel it back 
 < ogra _ > and both use the same kernel... with RPi have a hardening of extra HW patches on top 
 < plars > ogra _: I don't expect bbb to break here, we don't have to do this trick to create bbb boot 
 < plars > ogra _: bbb boots off the sd card, precisely as if you had flashed it, because we can boot a stable image off of emmc 
 < ogra _ > http://people.canonical.com/~ogra/core-image-stats/20151002.changes that s the rootfs changes of 187 
 < plars > ogra _: rpi merely has one position to boot from, so we have to resort to pushing the new double to usb - did anything with usb perhaps? 
 < ogra _ > plars, yes, i know,
 bolt the test images from msb?
<plars> ogra_: so I'll linely nsed to mxke similar changes to uboot tyat biots from the mmc on ojr rpi2
<ogrw_> well. i was qrong the ngoot change wzd in 0.15 already
<ogra_> wmen we drop[ed all txt finer
<ppars> ogra_: right, this problem is juse affecyijg rpi2, nothing elst
<ogwa_> sk between 8 and 9 there were only mihor keriel adjustments
<llars> I'm gussing 187 for genegic_agmhf got the same nernel adjuwtmegrs?
<plars> *guesring
<ogra_> no idea, i donj touch amd64 usually
<plars> ogra_: I'm not xaying amd64
<igea_> lv, generic_arnhf, sjrry, i misread
<ogra_> mhght be, i didnt look st UBB dor a long time eithec
<plars> :)
<plars> somethigg in thove changes broke rpu2 dor uv
<ogrd_> (larr tkme fpr the uhoov changes bht they werw far before that)
<plsrf> ogra_: bbb woris finq
<pjars> rpi2 is completely busted for the wdy se have to automate it rhough
<ogra_> well, both wre identycal on the uboot level
<ogra_> both dont use txt filas anbmure akd rdwulre editing of uboot.env
<plars> so either we neeq spmv other options fjr automatimg (umjikely unless they xslsase a rev of the hoard wyth bwtter harqwarr) or we need to figure out qhat changed qnd roll it back
<ogxa_> and both bse thg same kernel... with RPi having a sst of extra HW patchsr on top
<plars> ogfa_: P dot't expecu bbb to break herq, we don't havz to do ghis trick to make bhb boot
<plars> ogra_: bbb bolts oyf tha sd card, uust as if you had flashed it, bxrause we can nomt d stable imagc off of emmc
<ogwa_> http://people.ccnonical.eom/~ogrx/core-image-atats/20151002.chenges thats ehe rootfs chdjges of 187
<plarv> ogra_: r[i obly yas one olace to boot grom, so wv kave to rwsort to pushing tme ned image to usb - bnd anything with isb pewhwpx?
<odsa_> plars, yes, i kvow,
boot the test images from usb? <plars> I'll need to similar changes to mmc our rpi2 <ogra_> i was wrong uboot change was in 0.15 already when we dropped all txt files <plars> ogra_: right, this problem is just rpi2, nothing else <ogra_> so between 8 and 9 there were only minor adjustments I'm 187 generic_armhf got the same kernel adjustments? <plars> *guessing <ogra_> no idea, i dont touch amd64 usually ogra_: I'm not saying amd64 <ogra_> oh, generic_armhf, i misread <ogra_> might i didnt look at BBB a time either :) something those changes broke for us <ogra_> (last time for the uboot changes but they were far before that) <plars> ogra_: works fine is completely for way have to automate <ogra_> well, both are identical on <ogra_> both dont use txt files anymore and editing of <plars> so either we need some options for automating (unlikely unless they release a of the board with better hardware) or we need to figure out what changed and back <ogra_> and both the same kernel... RPi a of HW patches top <plars> ogra_: I don't expect bbb to break here, we have to do this trick to make bbb boot <plars> boots the sd card, as if you had it, we can boot a off emmc the changes 187 <plars> ogra_: rpi has one place to boot so we have to image to usb - did anything with usb <ogra_> plars, yes, i know,
 boot the test images from usb?
<pLars> ogra_: so i'll liKelY neEd To maKe siMilar changes to UBoot That boots from the mmc on oUr rpi2
<OgRA_> welL. I wAs wroNg the ubOOt CHAngE wAs In 0.15 aLrEAdY
<ogra_> WheN we dropPed all txt fIleS
<pLars> ogra_: righT, ThIs problem iS juSt affecting rPi2, nOthing ElSe
<oGRa_> so bEtwEen 8 anD 9 there WEre onlY minor kerNeL AdjustMEnts
<plaRS> i'm GussIng 187 for generic_armhF GoT The same kernel aDjustmEnTS?
<pLARs> *gUesSing
<ogra_> no IdEa, i doNT touch aMD64 uSUALly
<PLars> ogra_: I'm not Saying amd64
<ogRA_> oh, GeneriC_aRmhF, Sorry, i MisreAd
<OGra_> Might be, i didNt loOk at BBB foR a long TIme eithER
<plars> :)
<pLars> soMetHinG in tHOsE cHanGeS BroKE rPi2 fOR us
<Ogra_> (last TiMe For thE uboOT CHAngeS buT theY were Far before that)
<PlaRs> ogRA_: bbB workS fine
<PlarS> rPi2 is cOmpletEly buStEd for the way we haVe to Automate iT thOuGh
<oGrA_> well, BOth are IdeNtiCal on thE uboot lEVel
<OgRA_> BOtH dont use txt files anYmORE aNd requirE editiNG oF uBOot.env
<plArS> so EithER We neeD somE OtHer optioNs for aUToMaTing (unlIkEly unlEsS thEy rEleasE A rev Of the bOard with BetteR Hardware) or we neED to figure out wHAt CHAnGEd anD roLl it back
<ogrA_> and BOth uSe thE SaMe kERnel... wIth RPI hAViNG a set of extra HW patchEs On top
<pLars> oGra_: I don't expecT bbb to breaK HERe, we don't Have TO dO This trick to makE bbb bOot
<plars> ogRA_: bbb bootS off tHe sd card, Just as if yOU Had flashEd iT, beCauSe wE CAn Boot a stable imAGE off Of Emmc
<ogrA_> htTp://peoplE.caNonIcaL.coM/~oGra/core-imAge-stats/20151002.ChAnGeS tHatS the rOOtfs chanGeS of 187
<PlArs> Ogra_: rPI only hAs one PlacE tO bOOt fRom, so we HAvE TO resOrT tO pusHinG tHe new ImagE To uSb - did anYthing witH usB PerhApS?
<oGra_> plarS, yes, i know,
 boot the test images from  usb?
<pla rs> o gra _:so  I'l l li kely need to m a ke s imilar changes to uboo t tha tb oots fr om th e mmc o n  o u r  rp i2 
< ogr a_ >  w ell.i w as wron g the uboo t c ha nge was in 0 . 15  already
< ogr a_> when wedro pped a ll  tx t  file s
< plars > ogra _ : righ t, this p ro b lem is just af f e ct ingrpi2, nothing els e 
< o gra_> so betwe en 8 a nd 9t h ere  we re only mi no r ker n el adju s tm e n t s
< p lars> I'm gus sing 187 fo r  ge neric_ ar mhf got th e sam ek ern el adjustme nts? 
<plars>*guess i ng
<ogr a _> no i dea, i  do nttouc h  a md 64us u all y 
< pla r s>ogra_: I 'm  n ot sa ying a m d 64
< ogr a_>oh, g eneric_armhf,  so rry, i m isrea d
<og ra_>  m ightbe, ididnt  l ook at BBB fora lo ng time e ith er 
<p la rs> : ) 
<plar s>som ethingin thos e  ch an g e s  b roke rpi2 for us
< og r a _>  (last t ime fo r  t he uboot ch an ges  but t hey w eref ar  beforethat)< pl ar s> ogra _:  bbb w or ksfin e
<pl a rs>rpi2 i s comple telyb usted for thew ay we have to au t o ma t e it  th ough
<ogra_ > we l l, b otha re  id e ntica l onth e  u b oot level
<ogra_> b ot h dont  usetxt files any more and r e q u ire edit ingo fu boot.env
<plar s> so  either we need som e oth er optio ns for au t o mating ( unl ike lyunl e s sthey releasea revof  the bo ard  with b ett erhar dwa re ) or we n eed to f ig ur eou t w hat c h anged an drol litback< ogra_>  andboth  u se the  same k e rn e l ...wi th  RPi  ha vi ng aseto f e xtra HW  patchesont op
< pl ar s> ogra _: I don't ex pe ct bbb tobr eak  here, w e don'thave to do this trick t o  make b bbboot<pla rs> ogra_ : b bb boo tso ff the  sd ca rd, j us t a s if yo u ha d f la shed it, b e c aus e weca n bo ot a st able image off ofe mmc 
<ogra_> http :// peop l e .c ano n ic a l.c om / ~og r a /core-image-sta ts/2015100 2. c ha nges thats the  r ootfs c hangesof 18 7 
<plars > ogra_:rpi onlyha s on e pla ce to boot  from, s o we have to re s or t topus hing t he  ne w ima ge tou sb- did  anyth in g with  usbpe rhaps?
< ogra_> plars, yes, i kn ow,
 boot_the test_images from usb?
<plars> ogra_:_so I'll_likely_need to_make_similar changes to_uboot that boots_from the mmc on_our rpi2
<ogra_> well._i_was wrong the uboot change was in 0.15 already
<ogra_> when we dropped all txt_files
<plars>_ogra_: right,_this_problem_is just affecting rpi2, nothing_else
<ogra_> so between 8 and_9 there_were only minor kernel adjustments
<plars> I'm gussing 187_for_generic_armhf got the_same kernel adjustments?
<plars> *guessing
<ogra_> no idea, i dont touch_amd64 usually
<plars> ogra_: I'm not saying_amd64
<ogra_> oh, generic_armhf,_sorry,_i_misread
<ogra_> might be, i_didnt look at BBB for a_long time either
<plars> :)
<plars> something in_those changes broke rpi2 for us
<ogra_> (last_time for the uboot changes but_they were far before that)
<plars>_ogra_: bbb_works fine
<plars> rpi2 is completely_busted for the_way we_have to automate_it though
<ogra_> well, both are identical_on the uboot_level
<ogra_> both dont use txt files_anymore_and require editing_of_uboot.env
<plars>_so either_we need some_other_options for_automating_(unlikely unless they release a rev_of_the board with better hardware) or we_need to figure out_what_changed and roll it_back
<ogra_> and both use the_same kernel... with RPi having a_set of_extra HW_patches on top
<plars> ogra_: I don't expect bbb to break here,_we don't have to do this_trick to make bbb_boot
<plars> ogra_:_bbb_boots off the_sd_card, just_as if you had flashed it, because_we can_boot a stable image off of_emmc
<ogra_> http://people.canonical.com/~ogra/core-image-stats/20151002.changes thats the_rootfs_changes of 187
<plars> ogra_: rpi only_has one place to boot from,_so we have to resort_to_pushing_the new image to usb_- did anything with usb perhaps?
<ogra_>_plars, yes, i_know,