<lumag>
javierm, any particular reason for not using partitions?
<javierm>
lumag: it seems that's not working on the Chromebooks ?
<lumag>
javierm, Ah, I see
<javierm>
lumag: I've packaged rmtfs for Fedora and we try to stick as close as possible to the upstreams, so I don't want to downstream patch the existing rmtfs.service
<lumag>
javierm, Well, on non-ChromeOs devices you have to use partitions.
<lumag>
So you might have to ship two versions of the service
<lumag>
Or provide customisations
<javierm>
lumag: exactly :) That's why I added a rmtfs-dir.service
<lumag>
On Debian we use /etc/default/*
<javierm>
lumag: I plan to ship as two different sub-packages
<KieranBingham[m]>
lumag: Do you know anyone working on running debian on chromebooks? (Don't tell @javierm, but I'd like to see the HP-X2 work with Debian as well as it does for Fedora)
<lumag>
KieranBingham[m], no
* KieranBingham[m]
ducks ;-)
<javierm>
KieranBingham[m]: haha, I also use debian for my servers!
<lumag>
I use Debian, but this is on RB boards.
<javierm>
KieranBingham[m]: I love debian :)
<KieranBingham[m]>
;-)
<javierm>
I wish the Chromebooks behaved more like the WoA QC based laptops
<javierm>
that is, EFI-ish to boot, load the EFS data from a partition, etc
<javierm>
actually, I think that in the meantime will just ship both services since these will be disabled by default and document for users in the Fedora wiki what steps they need to take to get WiFi working
<javierm>
and enable the correct service manually depending on whether they have a WoA laptop or Chromebook
<lumag>
KieranBingham[m], and X13s / c630 don't have such troubles
mripard has joined #linux-msm
f_ has quit [Remote host closed the connection]
f_ has joined #linux-msm
pespin has quit [Remote host closed the connection]
<javierm>
KieranBingham[m]: AFAICT executing msm-cros-efs-loader.sh should be safe. It's also idempotent since the script checks if the path already exists and bails out if that's the case
<javierm>
but still I don't plan to be executed automatically and will let users know that have to execute themselves
<hexdump0815>
KieranBingham[m]: not as polished as the fedora stuff will be in the end, but maybe a good starting point in case you want to play around with debian on such devices
<KieranBingham[m]>
hexdump0815: aha thanks for the references. Are you working to get this upstream in debian too?
<javierm>
hexdump0815: the fedora support isn't as polished as you think :)
telent1 has joined #linux-msm
telent has quit [Ping timeout: 480 seconds]
telent has joined #linux-msm
telent1 has quit [Ping timeout: 480 seconds]
telent has quit [Ping timeout: 480 seconds]
telent has joined #linux-msm
<hexdump0815>
KieranBingham[m]: no - currently i'm at the limit of my time and energy to keep working images around for the different devices as it is just a spare time project of mine
<hexdump0815>
KieranBingham[m]: the idea is to make it easy for people to get started on those devices in the hope that more people help to get and keep them supported better and better
<KieranBingham[m]>
It's a shame. The aim of upstreaming is to reduce the amount you have to keep working. But I understand
<hexdump0815>
btw. there is also an irc channel for people working on linux on chromebooks: linux-cros-arm at oftc
<hexdump0815>
KieranBingham[m]: i fully agree, but it simply takes a lot of time to get the stuff upstreamed which i do not have right now, but i hope to be able to at some point with more time maybe
<hexdump0815>
i also tried to put together all i have learned so far about running linux on chromebooks at https://github.com/hexdump0815/linux-mainline-on-arm-chromebooks ... but all that gets a bit off topic for this channel - more maybe on the linux-cros-arm channel
<javierm>
hexdump0815: joined that channel. Thanks for pointing out