-
Notifications
You must be signed in to change notification settings - Fork 2k
Split of the camera documentation #2667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
naushir
commented
Oct 24, 2022
- Branch to split the camera documentation
- Restructure camera documentation
- camera: Update maximum exposure times
- camera: Update sensor module table
- camera: Remove "Software Features" section
- camera: Minor updates to the camera guide
Move the camera software documentation into a new section under Computres. Keep the camera hardware documenation in the existing Accessories space. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
Update the maximum exposure time numbers, and while at it, fold the table into the hardware comparison table above. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
- Remove Linux integration and C programming API rows - Update resolution list for imx219 and imx477 - Add imx477 sensor size Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
This does not belong in any camera documentation section. It ought to be re-instated in a future product sheet or product brief section. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
- s/Raspberry Pi is transitioning/Raspberry Pi has transitioned/ - Add audio-samplerate commandline option for libcamera-vid - Add dependencies for libav integration Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
@aallan here's a first pass at moving the camera documentation around. |
Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
|
||
=== `libcamera` and the legacy _Raspicam_ camera stack | ||
|
||
[NOTE] | ||
==== | ||
Raspberry Pi is transitioning from a legacy camera software stack based on proprietary Broadcom GPU code to an open-source stack based on `libcamera`. Raspberry Pi OS images from _Bullseye_ onwards will contain *only* the `libcamera`-based stack. Raspberry Pi OS images up to and including _Buster_ will contain the legacy _Raspicam_ stack, though the `libcamera` stack and applications can be installed xref:camera.adoc#libcamera-and-libcamera-apps-packages[using _apt_], or built by following the xref:camera.adoc#building-libcamera-and-libcamera-apps[normal build instructions]. | ||
Raspberry Pi has transitioned from a legacy camera software stack based on proprietary Broadcom GPU code to an open-source stack based on `libcamera`. Raspberry Pi OS images from _Bullseye_ onwards will contain *only* the `libcamera`-based stack. Raspberry Pi OS images up to and including _Buster_ will contain the legacy _Raspicam_ stack, though the `libcamera` stack and applications can be installed xref:camera.adoc#libcamera-and-libcamera-apps-packages[using _apt_], or built by following the xref:camera.adoc#building-libcamera-and-libcamera-apps[normal build instructions]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably this should get more extensive rewording. Perhaps also an admonition block, maybe something like:
NOTE: The lgacy firmware-based camera stack, including raspicam
, has been deprecated and will be removed in a future version of Raspberry Pi OS. To use the legacy camera stack, enable it using the raspi-config
utility: select legacy camera
under interface options
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will be removed in a future version of Raspberry Pi OS
It has already been removed in the current version of Raspberry Pi OS: "Raspberry Pi OS images from Bullseye onwards will contain only the libcamera
-based stack".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably this should get more extensive rewording. Perhaps also an admonition block, maybe something like:
NOTE: The lgacy firmware-based camera stack, including
raspicam
, has been deprecated and will be removed in a future version of Raspberry Pi OS. To use the legacy camera stack, enable it using theraspi-config
utility: selectlegacy camera
underinterface options
.
Hey. We're not really looking for external feedback on this branch at this time. Sorry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably this should get more extensive rewording
TBH, I don't really know what more I would change in the above paragraph. Suggestions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably this should get more extensive rewording. Perhaps also an admonition block, maybe something like:
NOTE: The lgacy firmware-based camera stack, includingraspicam
, has been deprecated and will be removed in a future version of Raspberry Pi OS. To use the legacy camera stack, enable it using theraspi-config
utility: selectlegacy camera
underinterface options
.Hey. We're not really looking for external feedback on this branch at this time. Sorry.
Not a problem. As you were.
As we now have both |
Maybe. The file name isn't really exposed in the text though, so it's "just" a backend thing that we can do at any point. |
Sure, I can do that change. |
Thanks for this @naushir. Just getting out of bed here in California, so I'll take a proper look at this after breakfast. Potentially we do minimal changes in this initial split, merge this in, and then the rewriting happens on a new branch after the merge? |
Ok, I'll leave this change as-is for now and if any crucial amendments need to be made before merging, let me know. |
Hey @naushir. You did your PR from your fork of the repo onto |
I'll now merge this onto the |
This looks like a good first cut to me. Looking at it, I think @lurch is right and the We also need some linking text between the two pages, and the How much new material do you think there is to go in @naushir ? |
Sure, I'll make that change.
There is a cross link between pages ("Preparing the SW" from the accessories page, and "Once installed..." from the camera software page). Perhaps this need to be more explicit? I'll also move the Raspicam stuff right to the end of the document.
Nothing more for now... I'll look though again, but I think I've made all the amendments required. |
@aallan and @lurch I've done something a bit silly unfortunately. I failed to see that this PR had already been merged into https://github.com/raspberrypi/documentation/tree/camera_branch. and I've gone ahead and made the above suggestions (including a bunch of file renames) in my branch at https://github.com/naushir/documentation/tree/camera. This is a non-FF merge, and overwrites changes in the existing PR :-( We could either force push the changes to camera_branch, or (preferably) removing the existing camera_branch and I create a new PR for camera_branch with my latest set of changes. What do you think? |
I'll leave it to @lurch to decide what's the best approach. His Git skills are superior to mine. Andrew? |
One option would be for either of you to create a new branch on here called camera_branch_v2, with the tip at 7b621a4. I can then create a PR with all my changes for camera_branch_v2 as normal, and we abandon camera_branch. |
If that is too troublesome, I can redo my work and base it on top of camera_branch. Let me know. |
I've (hopefully) just done this - let me know if it doesn't look right! |
Great, I'll push the PR now... |
See new PR at #2673 |
Closing in favour of #2673. |