Search results

After reading what hns wrote, I’m not convinced that a mount/unmount will be necessary. It will be managed at an even lower level than that (we can’t unmount the rootfs anyway). But it will still need to be managed such that the right device is attached at the right time and the kernel knows...

I see a few issues here. The first is if power is removed from the device. If power is removed randomly, it depends on the eMMC part itself to determine what happens in this situation. This may or may not be what’s happening, I have to take a look at the schematics. Entirely depends on how this...

Oh that’s interesting. I didn’t know that. That sounds like it would be a relatively complicated driver as it may have to handle mounting and unmounting the devices for the switch. I’ll check out the schematic.

PyraOS is Debian based and has the Debian repository keyrings. Anything on there can be installed via apt. Anything that isn’t a Debian package can usually be built from source. It seems Mate has been chosen as the default DE for PyraOS, but anything can be installed by the user.

Great, thanks aTc! I’ll take a look at these scripts and see what needs to be done to properly integrate them into the build system.

The charge circuit should support up to 2A. Right now it looks like the configuration is a little funky. The battery does not appear to charge fully and I haven’t been able to make measurements and fully characterize this yet. More to come once I’m able to do this. Ok that sounds good. I see...

Yep Mate is currently working without 3D. Here is a list of the outstanding issues I'm working on: * The battery monitor doesn't know the size of our battery yet (it uses some default values which are wrong). * The charger chip doesn't have a proper driver yet, so we are having some quirks...

Woo! Nice job hns!

Ok sounds good. I will work on setting up the Pyra remote in that fashion, since it sounds like you prefer that. For a decent example of merge requests, you can check out the merge request aTc and I used to get the base Pyra support patched in on the Pyra remote. You can easily view the diff...

Can the GitWeb interface handle merge requests? If so, can you turn this feature on? This is a much more public and interactive method for contributing than simply emailing patches to the mailing list.

@hns is the github for the Letux kernel (and U-Boot) active? It appears to track commits present on the official Letux kernel site, but it’s unclear if they are the same repository. If this github remote is active, can contributors such as myself push patches or WIP fix/feature branches in...

Hey everybody! Just wanted to let you know the build system is underway! It's relatively barebones at the moment but its open to clone and contribute. Right now its configured to clone my kernel fork and notaz's uboot fork, but that will be adjusted once everything from the beginning of this...

Yes the modules will need to be built against the specific kernel version. Yep this is one of the patches that aTc typically applies on top of the Letux kernel. Although calling it a patch I don’t think is particularly accurate since I don’t think there’s an actual patch file, just manual...

This is what I am working towards. Right now there are some scripts, but they only work on certain machines. I’ve already started to put together a docker based build system which will be aimed at both a clean development environment and a CI test environment which we can link up with gitlab...

Oops :)

I believe he tested it with this commit on the Pyra fork. https://dev.pyra-handheld.com/kernel/pyra-kernel/commit/6f43a75025cdddc73ab9c1eadde0b7c1aeaaeb2b This is just a fork of master at 4.19.60 with the necessary Pyra config patches applied. No significant investigation went into what went...

Makes sense, thanks guys :)

For this reason, what is the point of the DBP system? Why not just package everything as Debian packages. We have a dedicated Debian package repository for the Pyra.

SGX is one of my bigger concerns and one of the reasons I decided to fork. These drivers are barely maintained and poorly at that. They only work with very specific versions of the Linux kernel. Because of this, frequently updating the kernel is a bit of an issue. I plan on using repo to...

The Letux directory was removed because aTc has build errors when building the kernel package if it’s present. I haven’t been able to investigate this issue yet. I have no test platform, so at the moment I just build the zImage to make sure there are no errors before pushing for aTc to test...