John Stultz

@johnstultz_work

Linux Kernel Development, Timekeeping, Android Upstreaming, AOSP devboards. This my work specific account.

Vrijeme pridruživanja: veljača 2017.

Tweetovi

Blokirali ste korisnika/cu @johnstultz_work

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @johnstultz_work

  1. prije 9 sati

    Arnd's steady persistence on these fine-detail, major cross-kernel efforts is always so impressive! And somehow he manages to get tons of other work done all along the way!

    Poništi
  2. 5. velj

    Woe is they who hits <tab> after typing "tig "...

    Poništi
  3. proslijedio/la je Tweet
    1. velj

    I've decided to continue the blogging trend, this time around exploring Android Cuttlefish, a virtual platform for testing Android. I've been using it to test LTO and CFI with upstream LLVM, since that is maintained in kernel/common. Post:

    Poništi
  4. 30. sij

    Its cool to watch, but I also am terrified that in some future we'll all have to live-stream our development. <shudder>

    Prikaži ovu nit
    Poništi
  5. 30. sij

    Watching this is making me bummed about my failed volatile-ranges effort from a few years back. The video is really impressive! Implements the feature and user in ~two hours! Makes my two years of struggling to get code upstream look a little sad.

    Prikaži ovu nit
    Poništi
  6. 28. sij

    Oh! I was just thinking last week how I might work around my chromebook not supporting crostini ( ) with something like a WebUSB fastboot implementation. This looks *really* nice.

    Poništi
  7. 16. sij

    <Dancing about> "Buuuurn oooout!"

    Prikaži ovu nit
    Poništi
  8. 16. sij
    Prikaži ovu nit
    Poništi
  9. 13. pro 2019.

    And is it just me, or does everyone else read the word "schema" in there head in the voice of the gopher from winnie the pooh? ss<whistles>sssschema!

    Prikaži ovu nit
    Poništi
  10. 12. pro 2019.

    This week I submitted my first kernel dt binding patch in yaml. :P Galaxy-brain suspect this new requirement is really just cover for a gov re-training program for driver writers, for when we're forced to move on and get kubernetes jobs.

    Prikaži ovu nit
    Poništi
  11. 4. pro 2019.

    (you can imagine me wistfully sorting through your patches submitted for 3.10, pausing for a moment before putting them in the recycling. "Oh! bcache! And MCS locks again! *Sniff*")

    Prikaži ovu nit
    Poništi
  12. 4. pro 2019.

    Though, deleting 14.3% of my archive in time only freed up 8% of the space taken, so looks like this will start being a more-then-once-a-year thing

    Prikaži ovu nit
    Poništi
  13. 4. pro 2019.

    Its December, which means the gmail account I use for lkml reading is out of storage space again, and I have to delete another years worth of old messages. Goodbye 2013! You were a good one!

    Prikaži ovu nit
    Poništi
  14. 4. pro 2019.

    Imagine if we could hack on phones with such ease!

    Prikaži ovu nit
    Poništi
  15. 4. pro 2019.

    Nice overview demo from on the ChromeOS SuzyQ cable. I so so wish there was a real USB-C standard alternative interface for this sort of thing so we could get the same real debug UART functionality on most devices with a normal USB-C cable.

    Prikaži ovu nit
    Poništi
  16. 19. stu 2019.

    Yay. The Linux Plumbers' Android Micro-conference video is finally up!

    Poništi
  17. 1. stu 2019.

    Though I do wonder about the requiring physical presence for each auth op. That might be a monotonous pain for everyday use w/ git push/scp etc.

    Prikaži ovu nit
    Poništi
  18. 1. stu 2019.

    !!! While its not that functionally different from using gpg auth from yubikeys, the gpg setup on yubikeys is non-trivial and not something I'd want to walk a bunch of folks through. This seems like it will be easier. Plus U2F keys are cheaper!

    Prikaži ovu nit
    Poništi
  19. 16. lis 2019.

    Sorry for asking for twit-support, but do any ChromeOS folks know why fizz devices aren't getting updates? My box is *still* somehow stuck at 76. claims it should be getting 77. I've filed a bug, but not sure what else to do:

    Poništi
  20. 14. lis 2019.

    Since it was trusted location, I've had a ssh target that I do unencrypted rdiff-backups to. With the cloud I want something encrypted, but am a little wary of going full asymmetric encryption and having the potential of losing my key in earthquake/fire.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·