Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2018-06-19T18:12:44Zhttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/21Move information on x86 VM image out of volunteering section and expand2018-06-19T18:12:44ZBob HamMove information on x86 VM image out of volunteering section and expandThis is basically general reference information and isn't dependent on volunteering. Also, there should be more information on, for example, what to do with the .img image, which VM you can run it under, example command-lines for VM exe...This is basically general reference information and isn't dependent on volunteering. Also, there should be more information on, for example, what to do with the .img image, which VM you can run it under, example command-lines for VM execution, etc.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/20Separate information on open communication channels and volunteering2018-06-20T06:11:29ZBob HamSeparate information on open communication channels and volunteeringAs it is, the information on public mailing lists and chat rooms are under the "volunteering" chapter. This is something of a barrier because "volunteering" has implications beyond just the desire to ask questions or send drive-by patch...As it is, the information on public mailing lists and chat rooms are under the "volunteering" chapter. This is something of a barrier because "volunteering" has implications beyond just the desire to ask questions or send drive-by patches. I haven't volunteered to help any open source projects in many years but I've done a lot of work and sent many patches.
I think any communication channels that are generally open, like mailing lists and Matrix/IRC channels, should be described separately from volunteering and the communication channels which require formal "volunteer" status with LDAP logins and all that jazz.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/19Chapters should be reordered2018-11-19T17:40:50ZBob HamChapters should be reorderedIn my opinion, the documentation should be reordered. The most commonly referred-to information should come first. I found the Design chapter to be very far from the first thing I wanted to read. For example:
1. Introduction
2. Refer...In my opinion, the documentation should be reordered. The most commonly referred-to information should come first. I found the Design chapter to be very far from the first thing I wanted to read. For example:
1. Introduction
2. Reference information about hardware
3. Reference information about software
4. Instructions on setting up hardware, plugging in, getting a shell, etc.
5. Information about software development that's applicable to the phone, for example, say, descriptions of public phosh/oFono/Calls/virtual keyboard/etc. APIs
4. Instructions on setting up development environment(s)
5. Instructions on building software (current "App Development" chapter)
5. Guidelines for development (like Design)
6. Information on getting apps publishedhttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/18Need reference information2019-05-23T16:20:03ZBob HamNeed reference informationFeature: https://source.puri.sm/Librem5/use-cases/issues/93
As it is, the documentation is largely goal-oriented. For example:
"This site contains instruction and examples to help you accomplish your goals with the Librem 5 dev kit an...Feature: https://source.puri.sm/Librem5/use-cases/issues/93
As it is, the documentation is largely goal-oriented. For example:
"This site contains instruction and examples to help you accomplish your goals with the Librem 5 dev kit and phone."
As a developer, I find reference information more important than instruction.
For example, a table of all of the hardware components, like CPU, modem, audio codec, accelerometer, wlan, gnss, etc, together with links to datasheets. A good example is on page 41 (and possibly page 9) of the GTA04 manual:
https://projects.goldelico.com/p/gta04-main/downloads/47/
A table of the main software packages used on the hardware, together with links to their home page and/or source code would also be good. For example:
* Linux kernel, http://source.puri.sm/Librem5/linux-whatever
* U-Boot, ...
* PureOS, http://pureos.net
* Rootston, ...
* phosh, ...
* Calls, ...
* Web, ...
* Geary, ...
* Fractal, ...David BoddieDavid Boddiehttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/17Need general introduction to the dev kit and phone2018-12-29T22:59:02ZBob HamNeed general introduction to the dev kit and phoneFor the phone, something along the lines of:
"The Librem 5 is an i.MX8 phone running PureOS, a Debian derivative. The kernel is [based on NXP's sources? latest mainline with patches? not sure]. For the graphical windowing system, it ...For the phone, something along the lines of:
"The Librem 5 is an i.MX8 phone running PureOS, a Debian derivative. The kernel is [based on NXP's sources? latest mainline with patches? not sure]. For the graphical windowing system, it makes use of Rootston, a Wayland compositor, together with a bespoke shell named phosh. The graphical environment is based on the GNOME platform with a variety of modifications. The telephony stack consists of [oFono/ModemManager/etc.]. ... "
And something similar will be needed for the dev kit.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/16Use "dev board" instead of i.MX6 board2019-05-13T16:06:05ZGuido GuntherUse "dev board" instead of i.MX6 boardThe plasma mobile as well as the GNOME builder tutorial talk about the i.MX6 board. We should deprectate that wording and rather talks about "development" boards and rather link to the "Boards" chapter to make people pick the right dev b...The plasma mobile as well as the GNOME builder tutorial talk about the i.MX6 board. We should deprectate that wording and rather talks about "development" boards and rather link to the "Boards" chapter to make people pick the right dev board (nitrogen, devkit or phone).David BoddieDavid Boddiehttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/15"Boards" is in the left pane but not listed in the "Directory"2018-06-22T16:18:58ZGuido Gunther"Boards" is in the left pane but not listed in the "Directory"On the first page "Boads" shows up on the top left but no in the "Directory" in the center of the page. There are more inconsistencies (e.g. API Docs). That's probably fine but we should somewhere spell out what the directory and what th...On the first page "Boads" shows up on the top left but no in the "Directory" in the center of the page. There are more inconsistencies (e.g. API Docs). That's probably fine but we should somewhere spell out what the directory and what the left pane is used for.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/14Docs should be updated on commit2018-12-22T22:25:46ZGuido GuntherDocs should be updated on commitUpdating the docs is currently a manual task (AFAIK). It'd be great to publish them right after the Jenkins build.Updating the docs is currently a manual task (AFAIK). It'd be great to publish them right after the Jenkins build.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/13Make it more obvious where to ask questions2018-06-08T21:37:30ZGuido GuntherMake it more obvious where to ask questionshttps://developer.puri.sm/Volunteering/HowTo.html#getting-in-touch should make it more obvious where to ask which questions. We should have a URL
https://developer.puri.sm/Volunteering/HowTo.html#help
or similar in the docs that everyo...https://developer.puri.sm/Volunteering/HowTo.html#getting-in-touch should make it more obvious where to ask which questions. We should have a URL
https://developer.puri.sm/Volunteering/HowTo.html#help
or similar in the docs that everyone can post to direct people the public lists / instant messaging channelshttps://source.puri.sm/Librem5/image-builder/-/issues/5Launch image in qemu to run tests2022-04-29T19:22:19ZGuido GuntherLaunch image in qemu to run testsit would be good to launch the image in a qemu instance after build so we can run the test automatically.
See ```bin/test-testimge```.it would be good to launch the image in a qemu instance after build so we can run the test automatically.
See ```bin/test-testimge```.https://source.puri.sm/Librem5/image-builder/-/issues/4Upload built kernels2020-09-21T10:24:34ZGuido GuntherUpload built kernelsThe kernels are debs already (although not built like the Debian package), we should upload them so the can be installed via apt-get instead of fetching it from storage.puri.sm. Will make it simpler to fetch the latest kernel and to use ...The kernels are debs already (although not built like the Debian package), we should upload them so the can be installed via apt-get instead of fetching it from storage.puri.sm. Will make it simpler to fetch the latest kernel and to use different kernels for releases and ci builds.https://source.puri.sm/Librem5/image-builder/-/issues/3Package u-boot and m4.bin as Deb packages2020-09-21T10:24:34ZGuido GuntherPackage u-boot and m4.bin as Deb packagesFetching these things during the build cause trouble since it has to be in the correct folders on storage.puri.sm. Simply apt-get installing these things would solve these problems. u-boot is already packages in Debian, we should base th...Fetching these things during the build cause trouble since it has to be in the correct folders on storage.puri.sm. Simply apt-get installing these things would solve these problems. u-boot is already packages in Debian, we should base the packaging on it.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/12Need instructions on patch submittal2020-02-12T15:30:34ZHeather EllsworthNeed instructions on patch submittalEpic: https://source.puri.sm/Librem5/use-cases/issues/62
Where to get each code repo should be mentioned, along with instructions on how to submit a patch and the expected process.Epic: https://source.puri.sm/Librem5/use-cases/issues/62
Where to get each code repo should be mentioned, along with instructions on how to submit a patch and the expected process.Heather EllsworthHeather Ellsworthhttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/11Add architecture diagram of system2018-12-13T18:42:01ZHeather EllsworthAdd architecture diagram of systemA diagram is needed to show the architecture of the system. In the diagram, mentions of each code repo can be made (like phosh, the osk, etc). Then maybe below the diagram, we can list each code repo mentioned in the diagram with a link ...A diagram is needed to show the architecture of the system. In the diagram, mentions of each code repo can be made (like phosh, the osk, etc). Then maybe below the diagram, we can list each code repo mentioned in the diagram with a link to the repos.Heather EllsworthHeather Ellsworthhttps://source.puri.sm/Librem5/image-builder/-/issues/2Missing data/boot-ec-som.txt.in2018-06-05T19:05:54ZGuido GuntherMissing data/boot-ec-som.txt.inWhen building the ec-som image it fails for me like:
```
+ setup_uboot
+ sed -e s/##DTBNAME##/emcraft-imx8-som.dtb/ data/boot-ec-som.txt.in
sed: can't read data/boot-ec-som.txt.in: No such file or directory
+ cleanup_chroot
```
@angus....When building the ec-som image it fails for me like:
```
+ setup_uboot
+ sed -e s/##DTBNAME##/emcraft-imx8-som.dtb/ data/boot-ec-som.txt.in
sed: can't read data/boot-ec-som.txt.in: No such file or directory
+ cleanup_chroot
```
@angus.ainslie can you check in your boot-ec-som.txt.in ?https://source.puri.sm/Librem5/wlroots/-/issues/6Rootston freezes on ssh log out2023-07-24T09:06:31ZDorota CzaplejewiczRootston freezes on ssh log outAfter a couple of minutes of no activity, the lock screen will freeze, and its contents will not get updated no matter what.
The situation can be fixed by issuing `systemctl restart phosh`.
last lines of dmesg dmesg:
```
[ 4807.890960...After a couple of minutes of no activity, the lock screen will freeze, and its contents will not get updated no matter what.
The situation can be fixed by issuing `systemctl restart phosh`.
last lines of dmesg dmesg:
```
[ 4807.890960] etnaviv-gpu 130000.gpu: genpd_runtime_suspend()
[ 4828.364971] etnaviv-gpu 130000.gpu: genpd_runtime_resume()
[ 4828.900932] etnaviv-gpu 130000.gpu: genpd_runtime_suspend()
```https://source.puri.sm/Librem5/Apps_Issues/-/issues/28OTP application2019-01-15T16:12:53ZGuido GuntherOTP applicationUsers should be able to use their phone as OTP provider. A quick search showed up
https://github.com/paolostivanin/OTPClient
written in GTK+Users should be able to use their phone as OTP provider. A quick search showed up
https://github.com/paolostivanin/OTPClient
written in GTK+https://source.puri.sm/Librem5/image-builder/-/issues/1Drop imx6_CI_image_build and imx8_CI_image_build2019-03-26T10:49:17ZGuido GuntherDrop imx6_CI_image_build and imx8_CI_image_build@angus.ainslie We have
https://arm01.puri.sm/job/Images/job/imx6_CI_image_build/
and
https://arm01.puri.sm/job/Images/job/imx8_CI_image_build/
which do very similar things than the "Image Build" jobs, can these be removed?@angus.ainslie We have
https://arm01.puri.sm/job/Images/job/imx6_CI_image_build/
and
https://arm01.puri.sm/job/Images/job/imx8_CI_image_build/
which do very similar things than the "Image Build" jobs, can these be removed?https://source.puri.sm/Librem5/developer.puri.sm/-/issues/10mini tutorials2018-05-31T21:22:39ZGuido Gunthermini tutorials!1 mentions mini-tutorials but they don't seem to be part of the commit. Can you add them?!1 mentions mini-tutorials but they don't seem to be part of the commit. Can you add them?https://source.puri.sm/Librem5/developer.puri.sm/-/issues/9Boards chapter: Introductory paragraphs2019-05-13T16:24:47ZGuido GuntherBoards chapter: Introductory paragraphsIt would be nice if the big chapters would have an introductory paragraph. Let's the the boards chapter for now. What are these boards for, which one should I buy? Why are some of them TBD ?It would be nice if the big chapters would have an introductory paragraph. Let's the the boards chapter for now. What are these boards for, which one should I buy? Why are some of them TBD ?David BoddieDavid Boddie