├── Docker.readme ├── LICENSE ├── README.md ├── licenses ├── Broadcom ├── CC-Sampling-Plus-1.0 ├── LICENCE.broadcom-rpi-boot ├── LICENCE.broadcom_bcm43xx ├── bluez-firmware ├── freedist ├── linux-firmware ├── linux-fw-redistributable ├── no-source-code └── raspberrypi-videocore-bin └── reference ├── compile_run_benchmarks.sh ├── genup.pdf ├── migratation-from-sakaki-image.md ├── porthash.pdf └── showem.pdf /Docker.readme: -------------------------------------------------------------------------------- 1 | For use with Docker, please refer to necrose99's notes: 2 | 3 | https://github.com/necrose99/gentoo-on-rpi3-64bit/tree/master/Dockerstuff 4 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | {one line to give the program's name and a brief idea of what it does.} 635 | Copyright (C) {year} {name of author} 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | {project} Copyright (C) {year} {fullname} 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # gentoo-on-rpi-64bit 2 | Bootable 64-bit Gentoo image for the Raspberry Pi 4 Model B, Model Pi 3 B and B+, and Model Pi Zero 2 W, with Linux 5.4, OpenRC, Xfce4, VC4/V3D, camera & h/w codec support, profile 23.0 3 | 4 | 30 Oct 2020: sadly, due legal obligations arising from a recent change in Sakaki's 'real world' job, she stepped down from all maintenence roles related to Gentoo, leaving all her projects in limbo. 5 | 6 | This is the community maintained continuation of her work. Want to get involved? Open an issue here, or join the Discord server at https://discord.gg/a9VqTGHPy6 7 | 8 | ## Description 9 | 10 | [Raspberry Pi 4B, 3B and B+] 11 | 12 | This project is a bootable, microSD card **64-bit Gentoo image for the [Raspberry Pi 4 model B](https://www.raspberrypi.org/products/raspberry-pi-4-model-b/), ** single board computers (SBC). 13 | 14 | The image's userland contains a complete (OpenRC-based) Gentoo system (including a full Portage tree) - so you can run `emerge` operations immediately - and has been pre-populated with a reasonable package set (Xfce, LibreOffice, VLC, Kodi, GIMP, etc.) so that you can get productive *without* having to compile anything first! Unless you *want* to, of course; this being Gentoo, GCC, Clang, IcedTea (OpenJDK 8), Go, Rust and various versions of Python are of course bundled also ^-^ As of version 1.2.0 of the image, all userland software has been built under Gentoo's 17.0 profile, and, as of version 1.5.0 of the image, **the new RPi4 Model B is also supported** (and to reflect this, the project itself has been renamed, from `gentoo-on-rpi3-64bit` to `gentoo-on-rpi-64bit` ^-^). 15 | 16 | The kernel and userland are both 64-bit (`arm64`/`aarch64`), and support for the Pi's [VC4](https://wiki.gentoo.org/wiki/Raspberry_Pi_VC4) GPU (VC6 on the Pi4) has been included (using [`vc4-fkms-v3d`](https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=159853) / Mesa), so rendering performance is reasonable (e.g., `glxgears` between 400 and 1200fps, depending on load and system type; real-time video playback). The Pi's onboard Ethernet, WiFi (dual-band on the RPi3 B+ / Pi4 B) and Bluetooth adaptors are supported, as is the official 7" [touchscreen](#touchscreen) (if you have one). Sound works too, both via HDMI (given an appropriate display), and the onboard headphone jack. [Raspberry Pi Zero 2 W] 17 | As of version 1.1.0 of the image, a [weekly-autobuild binhost](#binhost), custom [Gentoo profile](#profile), and [binary kernel package](#binary_kp) have been provided, making it relatively painless to keep your system up-to-date (and, because of this, [`genup`](https://github.com/sakaki-/genup) has been configured to run [automatically once per week](#weekly_update), by default). As of version 1.4.0 of the image, access to the RPi3's hardware video codecs (and camera module, if you have one) [is supported](#v4l2) too, via the V4L2 framework, and, as of version 1.5.0, these features are available on the RPi4 also. Additionally, on the RPi4, the use of dual monitors is supported (but not required) as of version 1.5.0 (as is accelerated graphics, via V3D / Mesa). And, there is no 3GiB 'memory ceiling' anymore: if you are fortunate enough to own a 8GiB Pi4, all 8GiB of that RAM is usable. As of 1.5.2, [64-bit MMAL userland](#mmal) is supported (and used by bundled tools like `raspivid`), as is automated update of the RPi4's onboard EEPROM firmware. And finally, as of 1.6.0, `rpi-5.4.y` kernels are supported, the FOSS Jitsi videoconferencing server is bundled, and `elogind` is used in place of `consolekit`. 18 | 19 | 20 | Here's a screenshot of the image running on a dual-display RPi4 B (click to show a higher resolution view): 21 | 22 | [gentoo-on-rpi-64bit in use on Pi4 (screenshot)] 23 | 24 | The image may be downloaded from the link below (or via `wget`, per the instructions which follow). 25 | 26 | Variant | Version | Image 27 | :--- | ---: | ---: | 28 | Raspberry Pi 4B, 64-bit Full | N/A | N/A 29 | Raspberry Pi 4B 64-bit Lite | N/A | N/A 30 | Raspberry Pi 4B 64-bit Lite (systemd) | N/A | N/A 31 | 32 | **NB:** Currently as of January, 2024 we don't have up-to-date images as we are fixing our CI. Images are expected to be available again sometime during 2025. In the mean time, unofficial ones can be asked from our [Discord](https://discord.gg/Eu5D2e5KJQ). 33 | 34 | **NB:** **We are not officially supporting Raspberry Pi 3 boards anymore as of Febuary 2025 as we wish to focus on newer boards.** 35 | 36 | **NB:** most users will want the first, full image ([genpi64desktop-latest.img.zst](https://s3.genpi64.com/images/genpi64-arm64-openrc-desktop-alpha9.img.zst)) - the 'lite' variant ([genpi64-arm64-openrc-lite-alpha9.img.zst](https://s3.genpi64.com/images/genpi64-arm64-openrc-lite-alpha9.img.zst)) boots to a command-line (rather than a graphical desktop), and is intended only for experienced Gentoo users (who wish to to *e.g.* set up a server). 37 | 38 | Please read the instructions below before proceeding. Also please note that all images (and binary packages) are provided 'as is' and without warranty. You should also be comfortable with the (at the moment, unavoidable) non-free licenses required by the firmware and boot software supplied on the image before proceeding: these may be reviewed [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/tree/master/licenses). 39 | 40 | > It is sensible to install Gentoo to a **separate** microSD card from that used by your default Raspbian system; that way, when you are finished using Gentoo, you can simply power off, swap back to your old card, reboot, and your original system will be just as it was. 41 | 42 | ## Table of Contents 43 | 44 | - [Prerequisites](#prerequisites) 45 | - [Downloading and Writing the Image](#downloading-and-writing-the-image) 46 | * [Full Image (genpi64.img.zst)](#regularimage) 47 | * [Lite Image (genpi64lite.img.zst)](#liteimage) 48 | - [Booting!](#booting) 49 | - [Using Gentoo](#using-gentoo) 50 | - [Keeping Your System Up-To-Date](#keeping-your-system-up-to-date) 51 | * [Installing New Packages Under Gentoo](#installing-new-packages-under-gentoo) 52 | - [Miscellaneous Configuration Notes, Hints, and Tips](#miscellaneous-configuration-notes-hints-and-tips-skip) 53 | - [Maintenance Notes (Advanced Users Only)](#maintenance-notes-advanced-users-only-skip) 54 | * [Have your Gentoo PC Do the Heavy Lifting!](#have-your-gentoo-pc-do-the-heavy-lifting) 55 | * [Using your RPi3 as a Headless Server](#rpi3_headless) 56 | - [Miscellaneous Points (Advanced Users Only)](#miscellaneous-points-advanced-users-only-skip) 57 | * [RPi-Specific Ebuilds](#rpi-specific-ebuilds) 58 | * [New Features to Expedite Regular System Updating](#new-features-to-expedite-regular-system-updating) 59 | * [Subscribed Ebuild Repositories (aka Overlays)](#subscribed-ebuild-repositories-aka-overlays) 60 | - [Project Wiki](#projectwiki) 61 | - [Help Wanted!](#help-wanted) 62 | - [Acknowledgement](#acknowledgement) 63 | - [Feedback Welcome!](#feedback-welcome) 64 | 65 | ## Prerequisites 66 | 67 | To try this out, you will need: 68 | * For the **full** image (which most users will want), a [microSD](https://en.wikipedia.org/wiki/Secure_Digital) card of _at least_ 6GB capacity (as this image is 1GiB compressed, 5.5GiB uncompressed, so it should fit on any card marked as >= 8GB). For the **'lite'** image, a card marked as >= 4GB should suffice (as this image is 755MiB compressed, 3.5GiB uncompressed). If you intend to build many additional large packages (or kernels) on your RPi, a card of >16GB is recommended (the root partition will [automatically be expanded](#morespace) to fill the available space on your microSD card, on first boot). Depending on the slots available on your PC, you may also need an adaptor to allow the microSD card to be plugged in (to write the image to it initially). [Class A1 cards](https://www.raspberrypi.org/forums/viewtopic.php?p=1517864#p1517864) are particularly recommended, but not required. 69 | > I have found most SanDisk cards work fine; if you are having trouble, a good sanity check is to try writing the [standard Raspbian 32-bit image](https://www.raspberrypi.org/downloads/raspbian/) to your card, to verify that your Pi4 (or Pi3) will boot with it, before proceeding. 70 | 71 | * A Raspberry Pi 4 Model B, or Pi 3 Model B or B+ (obviously!). 72 | For simplicity, I am going to assume that you will be logging into the image (at least initially) via an (HDMI) screen and (USB) keyboard connected directly to your Pi, rather than e.g. via `ssh` (although, for completeness, it *is* possible to `ssh` in by editing `startup.sh` with networking details, explained in the [Lite Image section](#liteimage), or via the Ethernet interface (which has a DHCP client running), if you can determine the allocated IP address, for example from your router, or via [`nmap`](https://security.stackexchange.com/a/36200)). 73 | A [decent power supply](https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=138636) is recommended. 74 | 75 | * A PC to decompress the image and write it to the microSD card. This is most easily done on a Linux machine of some sort, but it is straightforward on a Windows or Mac box too (for example, by using [Etcher](https://etcher.io), which is a nice, all-in-one cross-platform graphical tool for exactly this purpose - it's free and open-source; or, bzt's [usbimager](https://gitlab.com/bztsrc/usbimager), a very lightweight cross-platform open source image writer). In the instructions below I'm going to assume you're using Linux. 76 | > It is possible to use your Raspberry Pi for this task too, if you have an external card reader attached, or if you have your root on e.g. USB (and take care to unmount your existing /boot directory before removing the original microSD card), or are booted directly from USB. Most users will find it simplest to write the image on a PC, however. 77 | 78 | ## Downloading and Writing the Image 79 | 80 | Choose either the full (recommended for most users) or 'lite' (command-line only) variant, then follow the appropriate instructions below ([full](#regularimage) or [lite](#liteimage)). 81 | 82 | > If you are using a Windows or Mac box, or prefer to use a GUI tool in Linux, I recommend you download your preferred image via your web browser using the [links](#downloadlinks) above, and then check out either of the the free, open-source, cross-platform tools [Etcher](https://etcher.io) or [usbimager](https://gitlab.com/bztsrc/usbimager) to write it to microSD card. Then, once you've done that, continue reading at ["Booting!"](#booting) below. 83 | 84 | > Alternatively, for those who prefer the Raspberry Pi [NOOBS](https://www.raspberrypi.org/documentation/installation/noobs.md) installer GUI, both images are now available for installation using [PINN](https://github.com/procount/pinn) (called `gentoo64` and `gentoo64lite` there). PINN is a fork of NOOBS and includes a number of additional advanced features. Please see [this post](https://forums.gentoo.org/viewtopic-p-8122236.html#8122236) for further details. *Many thanks to [procount](https://github.com/procount) for his work on this.* 85 | 86 | ### Full Image (`genpi64desktop-latest.img.zst`) 87 | 88 | On your Linux box, issue (you may need to be `root`, or use `sudo`, for the following, hence the '#' prompt): 89 | ```console 90 | # wget -c https://s3.genpi64.com/genpi-aarch64-desktop-latest.img.zst 91 | # zstd -d genpi64desktop-latest.img.zst -o genpi64desktop-latest.img 92 | ``` 93 | 94 | 95 | 96 | RPi4 Running Full Image 97 | 98 | to fetch the compressed disk image file (~1,961MiB). 99 | 100 | Next, insert (into your Linux box) the microSD card on which you want to install the image, and determine its device path (this will be something like `/dev/sdb`, `/dev/sdc` etc. (if you have a [USB microSD card reader](http://linux-sunxi.org/Bootable_SD_card#Introduction)), or perhaps something like `/dev/mmcblk0` (if you have e.g. a PCI-based reader); in any case, the actual path will depend on your system - you can use the `lsblk` tool to help you). Unmount any existing partitions of the card that may have automounted (using `umount`). Then issue: 101 | 102 | > **Warning** - this will *destroy* all existing data on the target drive, so please double-check that you have the path correct! As mentioned, it is wise to use a spare microSD card as your target, keeping your existing Raspbian microSD card in a safe place; that way, you can easily reboot back into your existing Raspbian system, simply by swapping back to your old card. 103 | 104 | ```console 105 | # dd if=genpi64desktop-latest.img of=/dev/sdX bs=1M status=progress; sync 106 | ``` 107 | Alternatively, you can use 108 | ```console 109 | # zstdcat -d genpi64desktop-latest.img.zst -vvv --no-sparse -o /dev/sdX 110 | ``` 111 | to write the compressed file directly. This doesn't require the 5GB of space on your local drive, and may be faster than using `dd`, but doesn't let you work with the image on your local computer *before* writing to the sd card. 112 | 113 | Substitute the actual microSD card device path, for example `/dev/sdc`, for `/dev/sdX` in the above command. Make sure to reference the device, **not** a partition within it (so e.g., `/dev/sdc` and not `/dev/sdc1`; `/dev/sdd` and not `/dev/sdd1` etc.) 114 | > If, on your system, the microSD card showed up with a path of form `/dev/mmcblk0` instead, then use this as the target, in place of `/dev/sdX`. For this naming format, the trailing digit *is* part of the drive name (partitions are labelled as e.g. `/dev/mmcblk0p1`, `/dev/mmcblk0p2` etc.). So, for example, you might need to use `zstdcat genpi64.img.zst --no-sparse -d -o /dev/mmcblk0 && sync`. 115 | 116 | The above `zstdcat` to the microSD card will take some time, due to the decompression (it takes between 5 and 25 minutes on my machine, depending on the microSD card used). It should exit cleanly when done - if you get a message saying 'No space left on device', then your card is too small for the image, and you should try again with a larger capacity one. 117 | > Note that on first boot, the image will _automatically_ attempt to resize its root partition (which, in this image, includes `/home`) to fill all remaining free space on the microSD card, by running [this startup service](https://github.com/sakaki-/genpi64-overlay/blob/master/sys-apps/rpi3-init-scripts/files/init.d_autoexpand_root-4); if you _do not_ want this to happen (for example, because you wish to add extra partitions to the microSD card later yourself), then simply **rename** the (empty) sentinel file `autoexpand_root_partition` (in the top level directory of the `vfat` filesystem on the first partition of the microSD card) to `autoexpand_root_none`, before attempting to boot the image for the first time. 118 | 119 | > **BTRFS Note** - the image uses btrfs, with significant compression to reduce the disk space used and file read time. The btrfs UUID is set at filesystem creation time, and cannot be changed on a live system. Only one device with any given btrfs UUID can be mounted at a time. To prevent possible problems with multiple copies of the image in use at once, after writing the image via `dd` or `zstdcat`, you should change the btrfs UUID via 120 | 121 | ```console 122 | # btrfstune -u /dev/sdX2 123 | ``` 124 | 125 | This will generate a new, random, uuid for the second partition. In the future we want to do this on first boot, but it must be done *before* the root filesystem is mounted. 126 | 127 | Now continue reading at ["Booting!"](#booting) below. 128 | 129 | ### Lite Image (`genpi64lite.img.xz`) 130 | 131 | > Please note: this image boots to a command line, not a GUI, and is only suitable for experienced Gentoo users. If unsure, choose the [full image](#regularimage) above, instead. 132 | 133 | On your Linux box, issue (you may need to be `root`, or use `sudo`, for the following, hence the '#' prompt): 134 | ```console 135 | # wget -c https://s3.genpi64.com/images/genpi-arm64-lite-latest.img.zst 136 | # zstd -d genpi64-arm64-lite-latest.img.zst -o genpi64-arm64-lite-latest.img 137 | ``` 138 | 139 | [RPi4 Running Lite Image] 140 | 141 | to fetch the compressed disk image file (~956MiB) 142 | 143 | 144 | Next, insert (into your Linux box) the microSD card on which you want to install the image, and determine its device path (this will be something like `/dev/sdb`, `/dev/sdc` etc. (if you have a [USB microSD card reader](http://linux-sunxi.org/Bootable_SD_card#Introduction)), or perhaps something like `/dev/mmcblk0` (if you have e.g. a PCI-based reader); in any case, the actual path will depend on your system - you can use the `lsblk` tool to help you). Unmount any existing partitions of the card that may have automounted (using `umount`). Then issue: 145 | 146 | > **Warning** - this will *destroy* all existing data on the target drive, so please double-check that you have the path correct! As mentioned, it is wise to use a spare microSD card as your target, keeping your existing Raspbian microSD card in a safe place; that way, you can easily reboot back into your existing Raspbian system, simply by swapping back to your old card. 147 | 148 | ```console 149 | # dd if=genpi64-arm64-lite-latest.img of=/dev/sdX bs=1M status=progress; sync 150 | ``` 151 | 152 | Substitute the actual microSD card device path, for example `/dev/sdc`, for `/dev/sdX` in the above command. Make sure to reference the device, **not** a partition within it (so e.g., `/dev/sdc` and not `/dev/sdc1`; `/dev/sdd` and not `/dev/sdd1` etc.) 153 | > If, on your system, the microSD card showed up with a path of form `/dev/mmcblk0` instead, then use this as the target, in place of `/dev/sdX`. For this naming format, the trailing digit *is* part of the drive name (partitions are labelled as e.g. `/dev/mmcblk0p1`, `/dev/mmcblk0p2` etc.). So, for example, you might need to use `xzcat genpi64lite.img.xz -d --no-sparse -o /dev/mmcblk0 && sync`. 154 | 155 | The above `xzcat` to the microSD card will take some time, due to the decompression (it takes between 5 and 10 minutes on my machine, depending on the microSD card used). It should exit cleanly when done - if you get a message saying 'No space left on device', then your card is too small for the image, and you should try again with a larger capacity one. 156 | 157 | Now continue reading at ["Booting!"](#booting), immediately below. Note, however, that in the case of this 'lite' image, after the startup / resize process has completed, you will be landed at a console login prompt (although it is simple enough to [parlay to a basic X11 desktop](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Setup-a-Simple-X11-Desktop-Environment-on-the-Lite-Image) if you wish). The login credentials are the same as for the full image, *viz.*: 158 | * default user **demouser**, password **Raspberrypi64!**; 159 | * **root** user password also **GenPi64@**. 160 | 161 | 162 | ## Booting! 163 | 164 | Begin with your RPi4 (or RPi3) powered off. Remove the current (Raspbian or other) microSD card from the board (if fitted), and store it somewhere safe. 165 | 166 | Next, insert the (Gentoo) microSD card you just wrote the image to into the Pi. Ensure you have peripherals connected (with the main display plugged into the **HDMI0** port - the one nearer the USB-C power connector - if using an RPi4), and apply power. 167 | 168 | You should see the Pi's standard 'rainbow square' on-screen for about 2 seconds, then the display will go blank for about 10 seconds, and then (once the graphics driver has loaded) a text console will appear, showing OpenRC starting up. On this first boot (unless you have renamed the sentinel file `autoexpand_root_partition` in the microSD card's first partition to `autoexpand_root_none`), the system will, after a further 10 seconds or so, _automatically resize_ the root partition to fill all remaining free space on the drive, and, having done this, reboot (to [allow the kernel to see](http://unix.stackexchange.com/questions/196435/is-it-possible-to-enlarge-the-partition-without-rebooting) the new partition table). As of October 10, 2022, the resizing script expands the partition, but fails to expand the btrfs system; see Issue #35. To expand the btrfs file system, execute: 169 | 170 | ```console 171 | # btrfs filesystem resize max / 172 | ``` 173 | 174 | You should then see the 'rainbow square' startup sequence once more, and then the system will resize its root filesystem, to fill the newly enlarged partition. Once this is done, it will launch a standard Xfce desktop, logged in automatically to the pre-created `demouser` account. A simple configuration application will also be autostarted; this allows you to e.g. change screen resolution, if required: 175 | 176 | [Baseline Xfce desktop] 177 | 178 | > If your display looks OK, there's no need to make any changes immediately - just click OK to dismiss the welcome dialog, and then click on the Cancel button to close out the configuration tool itself. 179 | 180 | The whole process (from first power on to graphical desktop) should take less than three minutes or so (on subsequent reboots, the resizing process will not run, so startup will be a _lot_ faster). 181 | 182 | > The initial **root** password on the image is **GenPi64@**. The password for **demouser** is also **Raspberrypi64!** (you may need this if e.g. the screen lock comes on; you can also do `sudo su --login root` to get a root prompt at the terminal, without requiring a password). These passwords are set by the [`autoexpand-root`](https://github.com/sakaki-/genpi64-overlay/blob/master/sys-apps/rpi3-init-scripts/files/init.d_autoexpand_root-4) startup service. Note that the screensaver for `demouser` has been disabled by default on the image. 183 | 184 | > NB - if your connected computer monitor or TV output appears **flickering or distorted**, you may need to change the settings in the file `config.txt`, located in the microSD card's first partition (this partition is formatted `vfat` so you should be able to edit it on any PC; alternatively, when booted into the image, it is available at `/boot/config.txt`). Any changes made take effect on the next restart. For an explanation of the various options available in `config.txt`, please see [these notes](https://www.raspberrypi.org/documentation/configuration/config-txt/README.md) (the [shipped defaults](https://github.com/sakaki-/genpi64-overlay/blob/master/sys-boot/rpi3-boot-config/files/config.txt-9) should work fine for most users, however). As of v1.3.1 of this image, you can also use the bundled GUI tool (shown in the screenshot above) to modify (some of) these settings. The program, `pyconfig_gen`, is, as noted, automatically started on first login, and is available under Applications→Settings→RPi Config Tool. 185 | 186 | > If the edges of the desktop appear "clipped" by your display (this mostly happens when using HDMI TVs), issue `sudo mousepad /boot/config.txt`, comment out the line `disable_overscan=1` (so it reads instead `#disable_overscan=1`), save the file, and then reboot (from v1.3.1, you can also enable and configure overscan via the Rpi Config Tool, as noted above). Please note that with modern boot firmware, [overscan is ignored](https://github.com/raspberrypi/linux/issues/3059#issuecomment-510108535) if a DMT mode is set. 187 | 188 | > Tip: if you'd like to set up a persistent dual-monitor setup on an RPi4, please see my short tutorial on this project's open wiki [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Set-Up-Dual-Displays-on-your-RPi4) (this also contains useful hints for setting up a single display). 189 | 190 | ## Using Gentoo 191 | 192 | The supplied image contains a fully-configured `arm64` Gentoo system (*not* simply a [minimal install](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Media#Minimal_installation_CD) or [stage 3](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Media#What_are_stages_then.3F)), with a complete Portage tree already downloaded, so you can immediately perform `emerge` operations etc. Be aware that, as shipped, it uses **UK locale settings, keyboard mapping, timezone and WiFi regulatory domain**; however, these are easily changed if desired. See the Gentoo Handbook ([here](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base#Timezone) and [here](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/System#Init_and_boot_configuration)) for details on the first three; to customize the WiFi regulatory domain, start the Applications→Settings→RPi Config Tool app, select the WiFi tab, choose your location from the drop-down, click Save and Exit, and reboot when prompted. 193 | 194 | > Please note that for non-UK keyboards, **prior** to v1.5.4 of the image, you will also need to edit the file `/etc/X11/xorg.conf.d/00-keyboard.conf` and replace `gb` in the line `Option "XkbLayout" "gb"` with the appropriate code from [this list](https://pastebin.com/v2vCPHjs). Leave the rest of the file as-is, save, then reboot for the change to take effect. You will need to be the `root` user, or use `sudo` to edit this file (e.g., type `sudo mousepad /etc/X11/xorg.conf.d/00-keyboard.conf` in a terminal). **From** v1.5.4 however, a simpler GUI-driven method is available. Simply click Applications→Settings→Keyboard, select the Layout tab, ensure Use system defaults is _unchecked_, and then, in the Keyboard layout section, click on Add to insert the layouts you need to use. For example, the image has `English (UK)` and `English (US)` selected, but you should obviously choose whatever works for you. Do not add more than four layouts (or the switcher plugin will not work correctly). You can use the arrow keys to re-order the list (if you have more than one layout); the one at the _top_ will be the default activated at login time. Once done, click on Close to dismiss the dialog. You should now find that you can switch layouts (if you have specified more than one) either by clicking on the top panel-bar keyboard plugin (the one next to the `Demo User` text on the far right) or by pressing the hotkey (by default, this is Windows KeySpace). 195 | 196 | If you have an RPi4, and would like to configure a **dual monitor** setup, please see [these notes](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Set-Up-Dual-Displays-on-your-RPi4) (also contains some useful hints for single monitor deployment, applicable to all models). 197 | 198 | If you wish to add Bluetooth peripherals (e.g., a wireless mouse and/or keyboard) to your RPi, please see [below](#add_bt_device). 199 | 200 | If you would like to run **benchmarks** on your RPi system, please see [these notes](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Effective-Benchmarking-on-your-64-Bit-RPi-System). 201 | 202 | For hardware-accelerated YouTube playback, please see [this post](https://www.raspberrypi.org/forums/viewtopic.php?p=1589280#p1589280). Also please note that as of v1.5.4 of the image, you can (particularly on a Pi4B with a fast Internet connection) use Applications→Internet→SMTube (YouTube, Hi-Res) to play back videos from YouTube in 1080p, where available; this is significantly better than the currently bundled browsers (Firefox and Chromium) can achieve. 203 | 204 | The `@world` set of packages (from `/var/lib/portage/world`) pre-installed on the image may be viewed [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/blob/master/reference/world-packages) (note that the version numbers shown in this list are Gentoo ebuilds, but they generally map 1-to-1 onto upstream package versions). 205 | > The *full* package list for the image (which includes @system and dependencies) may also be viewed, [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/blob/master/reference/world-all-packages). 206 | 207 | The system on the image has been built via a minimal install system and stage 3 from Gentoo (`arm64`, available [here](http://distfiles.gentoo.org/experimental/arm64/)), but _all_ binaries (libraries and executables) have been rebuilt (with profile 17.0) to run optimally on the Raspberry Pi 4 B's Cortex-A72-based SoC, while still retaining backwards compatibility with the older Pi 3 (B and B) model's Cortex-A53. The `/etc/portage/make.conf` file used on the image may be viewed [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/blob/master/reference/make.conf), augmented by the [custom profile's](#profile) [`make.defaults`](https://github.com/sakaki-/genpi64-overlay/tree/master/profiles/targets/rpi3/make.defaults). The `CHOST` on the image is `aarch64-unknown-linux-gnu` (per [these notes](https://wiki.gentoo.org/wiki/User:NeddySeagoon/Pi3#Getting_Started)). All packages have been brought up to date against the Gentoo tree as of 11 June 2020. The image contains *two* kernels: one ([`bcmrpi3-kernel-bis`](https://github.com/sakaki-/bcmrpi3-kernel-bis)) is used when booting on the RPi3 B/B+, and the other ([`bcm2711-kernel-bis`](https://github.com/sakaki-/bcm2711-kernel-bis)) when booting on an RPi4. The correct kernel is chosen automatically at boot time. Each kernel has a distinct release name, and so a separate module set in `/lib/modules/`. 208 | 209 | > Note: the `CFLAGS` used for the image build is `-march=armv8-a+crc -mtune=cortex-a72 -O2 -pipe`. You can of course re-build selective components with more aggressive flags yourself, should you choose. As the SIMD FPU features are standard in ARMv8, there is no need for `-mfpu=neon mfloat-abi=hard` etc., as you would have had on e.g. the 32-bit ARMv7a architecture. Note that AArch64 NEON also has a full IEEE 754-compliant mode (including handling denormalized numbers etc.), there is also no need for `-ffast-math` flag to fully exploit the FPU either (again, unlike earlier ARM systems). Please refer to the official [Programmer’s Guide for ARMv8-A](http://infocenter.arm.com/help/topic/com.arm.doc.den0024a/DEN0024A_v8_architecture_PG.pdf) for more details. Neither the Pi3 nor Pi4 is shipped with the ARMv8 hardware crypto extensions enabled, unfortunately. 210 | 211 | When logged in as `demouser`, it is sensible to change the password (from `raspberrypi64`) and `root`'s password (also from `raspberrypi64`). Open a terminal window and do this now: 212 | ```console 213 | demouser@pi64 ~ $ passwd 214 | Changing password for demouser. 215 | (current) UNIX password: 216 | New password: 217 | Retype new password: 218 | passwd: password updated successfully 219 | demouser@pi64 ~ $ su - 220 | Password: 221 | pi64 ~ # passwd 222 | New password: 223 | Retype new password: 224 | passwd: password updated successfully 225 | pi64 ~ # exit 226 | logout 227 | demouser@pi64 ~ $ 228 | ``` 229 | 230 | If you want to create your own account, you can do so easily. Open a terminal, su to root, then issue (adapting with your own details, obviously!): 231 | ```console 232 | pi64 ~ # useradd --create-home --groups "adm,disk,lp,wheel,audio,video,cdrom,usb,users,plugdev,portage,cron,gpio,i2c,spi" --shell /bin/bash --comment "Sakaki" sakaki 233 | pi64 ~ # passwd sakaki 234 | New password: 235 | Retype new password: 236 | passwd: password updated successfully 237 | ``` 238 | 239 | You can then log out of `demouser`, and log into your new account, using the username and password just set up. When prompted with the `Welcome to the first start of the panel` dialog, select Use default config, as this provides a useful 'starter' layout. 240 | 241 | > Depending on how quickly you select Use default config, you *may* find you are left with a black desktop background. This issue should resolve itself after your next login, however. 242 | 243 | Then, once logged in, you can delete the `demouser` account if you like. Open a terminal, `su` to root, then: 244 | ```console 245 | pi64 ~ # userdel --remove demouser 246 | userdel: demouser mail spool (/var/spool/mail/demouser) not found 247 | ``` 248 | > The mail spool warning may safely be ignored. Also, if you want your new user to be automatically logged in on boot (as `demouser` was), substitute your new username for `demouser` in the file `/etc/lightdm/lightdm.conf.d/50-autologin-demouser.conf` (and if you do _not_ want autologin, this file may safely be deleted). 249 | 250 | One hint worth bearing in mind: desktop compositing is on for new users by default (unless you are using a Pi3 and have a very high-resolution display, when it will automatically be turned off for you). This gives nicely rendered window shadows etc. but if you find video playback framerates (from `VLC` etc.) are too slow, try turning it off (Applications→Settings→Window Manager Tweaks, Compositor tab). 251 | 252 | > Note that as of version 1.1.2 of the image, a number of Xfce 'fixups' will automatically be applied when a new user logs in for the first time; these include:
1) synchronizing compositing to the vertical blank (without which menus flash annoyingly under VC4);
2) setting window move and resize opacity levels; and
3) ensuring the desktop background displays on login (otherwise it often stays black; note that this fix sometimes does not work for the *first* login of a new user, as noted [above](black_background_first_login)).
They are managed by the `xfce-extra/xfce4-fixups-rpi3` package (which inserts an entry into `/etc/xdg/autostart/`). 253 | 254 | ## Keeping Your System Up-To-Date 255 | 256 | You can update your system at any time. As there are quite a few steps involved to do this correctly on Gentoo, I have provided a convenience script, `genup` ([source](https://github.com/sakaki-/genup), [manpage](https://github.com/sakaki-/gentoo-on-rpi-64bit/blob/master/reference/genup.pdf)) to do this as part of the image. 257 | 258 | Of course, you can always use `genup` directly (as root) to update your system at any time. See the [manpage](https://github.com/sakaki-/gentoo-on-rpi-64bit/blob/master/reference/genup.pdf) for full details of the process followed, and the options available for the command. 259 | 260 | > Bear in mind that a `genup` run will take around three to six hours to complete, even if all the necessary packages are available as binaries on the [binhost](#binhost). Why? Well, since Gentoo's [Portage](https://wiki.gentoo.org/wiki/Portage) - unlike most package managers - gives you the flexibility to specify which package versions and configuration (via USE flags) you want, it has a nasty graph-theoretic problem to solve each time you ask to upgrade (and it is mostly written in Python too, which doesn't help ^-^). Also, many of the binary packages are themselves quite large (for example, the current `libreoffice` binary package is >100MiB) and so time-consuming to download (unless you have a very fast Internet connection). 261 | 262 | When an update run has completed, if prompted to do so by genup (directly, or at the tail of the `/var/log/latest-genup-run.log` logfile), then issue: 263 | ```console 264 | pi64 ~ # dispatch-conf 265 | ``` 266 | to deal with any config file clashes that may have been introduced by the upgrade process. 267 | 268 | For more information about Gentoo's package management, see [my notes here](https://wiki.gentoo.org/wiki/Sakaki's_EFI_Install_Guide/Installing_the_Gentoo_Stage_3_Files#Gentoo.2C_Portage.2C_Ebuilds_and_emerge_.28Background_Reading.29). 269 | 270 | ### Installing New Packages Under Gentoo 271 | 272 | > The following is only a *very* brief intro to get you started. For more information, see the [Gentoo handbook](https://wiki.gentoo.org/wiki/Handbook:AMD64/Working/Portage). 273 | 274 | You can add any additional packages you like to your RPi. To search for available packages, you can use the (pre-installed) [`eix` tool](https://wiki.gentoo.org/Eix). For example, to search for all packages with 'hex editor' in their description: 275 | 276 | ```console 277 | demouser@pi64 ~ $ eix --description --compact "hex.editor" 278 | [N] app-editors/curses-hexedit (--): full screen curses hex editor (with insert/delete support) 279 | [N] app-editors/dhex (--): ncurses-based hex-editor with diff mode 280 | [N] app-editors/hexcurse (--): ncurses based hex editor 281 | [N] app-editors/lfhex (--): A fast hex-editor with support for large files and comparing binary files 282 | [N] app-editors/qhexedit2 (--): Hex editor library, Qt application written in C++ with Python bindings 283 | [N] app-editors/shed (--): Simple Hex EDitor 284 | [N] app-editors/wxhexeditor (--): A cross-platform hex editor designed specially for large files 285 | [N] dev-util/bless (--): GTK# Hex Editor 286 | Found 8 matches 287 | ``` 288 | (your output may vary). 289 | 290 | Then, suppose you wanted to find out more about one of these, say `shed`: 291 | 292 | ```console 293 | demouser@pi64 ~ $ eix --verbose app-editors/shed 294 | * app-editors/shed 295 | Available versions: *1.12 *1.13 ~*1.15 296 | Homepage: http://shed.sourceforge.net/ 297 | Find open bugs: https://bugs.gentoo.org/buglist.cgi?quicksearch=app-editors%2Fshed 298 | Description: Simple Hex EDitor 299 | License: GPL-2 300 | 301 | ``` 302 | (again, your output may vary, depending upon the state of the Gentoo repo at the time you run the query, your version of `eix`, etc.) 303 | 304 | That '\*' in front of versions 1.12 and 1.13 indicates that the package has *not* yet been reviewed by the Gentoo devs for the `arm64` architecture, but that its versions 1.12 and 1.13 *have* been reviewed as stable for some other architectures (in this case, `amd64`, `ppc` and `x86` - you can see this by reviewing the matching ebuilds, at `/usr/portage/app-editors/shed/shed-1.12.ebuild` and `/usr/portage/app-editors/shed/shed-1.13.ebuild`). Version 1.15 is also marked as being in testing (the '\~\*') for those (other) architectures. 305 | 306 | However, you will find that most packages (which don't have e.g. processor-specific assembly or 32-bit-only assumptions) *will* build fine on `arm64` anyway, you just need to tell Gentoo that it's OK to try. 307 | 308 | To do so for this package, become root, then issue: 309 | 310 | ```console 311 | pi64 ~ # echo "app-editors/shed * ~*" >> /etc/portage/package.accept_keywords/shed 312 | ``` 313 | 314 | > The above means to treat as an acceptable build candidate any version marked as *stable* on any architecture (the '*\') or as *testing* on any architecture (the '\~\*'). The second does *not* imply the first - for example, `shed-1.12` is not marked as testing on any architecture at the time of writing, so just '~\*' wouldn't match it. 315 | 316 | Then you can try installing it, using [`emerge`](https://wiki.gentoo.org/wiki/Portage): 317 | ```console 318 | pi64 ~ # emerge --verbose app-editors/shed 319 | 320 | These are the packages that would be merged, in order: 321 | 322 | Calculating dependencies... done! 323 | [ebuild N *] app-editors/shed-1.15::gentoo 86 KiB 324 | 325 | Total: 1 package (1 new), Size of downloads: 86 KiB 326 | 327 | >>> Verifying ebuild manifests 328 | >>> Emerging (1 of 1) app-editors/shed-1.15::gentoo 329 | >>> Installing (1 of 1) app-editors/shed-1.15::gentoo 330 | >>> Recording app-editors/shed in "world" favorites file... 331 | >>> Jobs: 1 of 1 complete Load avg: 1.25, 0.56, 0.21 332 | >>> Auto-cleaning packages... 333 | 334 | >>> No outdated packages were found on your system. 335 | 336 | * GNU info directory index is up-to-date. 337 | ``` 338 | 339 | Once this completes, you can use your new package! 340 | 341 | > Note that if you intend to install complex packages, you may find it easier to set `ACCEPT_KEYWORDS="* ~*"` in `/etc/portage/make.conf`, since many packages are not yet keyworded for `arm64` yet on Gentoo. Obviously, this will throw up some false positives, but it will also mostly prevent Portage from suggesting you pull in 'live' (aka `-9999`, aka current-tip-of-source-control) ebuilds, which can easily create a nasty dependency tangle. 342 | 343 | Once you get a package working successfully, you can then explicitly keyword its dependencies if you like (in `/etc/portage/package.accept_keywords/...`), rather than relying on `ACCEPT_KEYWORDS="* ~*"` in `/etc/portage/make.conf`. Should you do so, please feel free to file a PR against the [`genpi64:default/linux/arm64/17.0/desktop/genpi64` profile](https://github.com/sakaki-/genpi64-overlay/tree/master/profiles/targets/rpi3) with your changes, so that others can benefit (I intend to submit keywords from this profile to be considered for inclusion in the main Gentoo tree, in due course). 344 | 345 | Have fun! ^-^ 346 | 347 | > If you need to install a particular package that isn't currently in the Gentoo tree, note that it _is_ possible to install binary packages from Raspbian (or other 32-bit repos) on your 64-bit system. For further details, please see [these notes](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Running-32-bit-Raspbian-Packages-on-your-64-bit-Gentoo-System). 348 | 349 | > Alternatively, to install source packages with highly resource-intensive build profiles (such as `dev-lang/rust`), you can temporarily mount the image within a `binfmt_misc` QEMU user-mode `chroot` on your Linux PC, and perform the `emerge` there. This technique allows you to easily leverage the increased memory and CPU throughput of your regular desktop machine. For further details, please see my wiki tutorial [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Build-aarch64-Packages-on-your-PC%2C-with-User-Mode-QEMU-and-binfmt_misc). 350 | 351 | ## Miscellaneous Configuration Notes, Hints, and Tips (↓[skip](#maintnotes)) 352 | 353 | You don't need to read the following notes to use the image, but they may help you better understand what is going on! 354 | 355 | * Because the Pi has no battery-backed real time clock (RTC), I have used the `swclock` (rather than the more usual `hwclock`) OpenRC boot service on the image - this simply sets the clock on boot to the recorded last shutdown time. An NTP client, `chronyd`, is also configured, and this will set the correct time as soon as a valid network connection is established. 356 | > Note that this may cause a large jump in the time when it syncs, which in turn will make the screensaver lock come on. Not a major problem, but something to be aware of, as it can be quite odd to boot up, log in, and have your screen almost immediately lock! For this reason, the `demouser` account on the image has the screensaver disabled by default. 357 | 358 | * The image is configured with `NetworkManager`, so achieving network connectivity should be straightforward. The Ethernet interface is initially configured as a DHCP client, but obviously you can modify this as needed. Use the NetworkManager applet (top right of your screen) to do this; you can also use this tool to connect to a WiFi network. 359 | > Note that getting WiFi to work on the RPi3/4 requires appropriate firmware (installed in `/lib/firmware/brcm`): this is managed by the `sys-firmware/brcm43430-firmware` package (see [below](#wifi)). On the RPi3 B+ and RPi4 B, dual-band WiFi is supported. 360 | 361 | * Bluetooth *is* operational on this image, but since, by default, the Raspberry Pi 3 [uses the hardware UART](http://www.briandorey.com/post/Raspberry-Pi-3-UART-Overlay-Workaround) / `ttyAMA0` to communicate with the Bluetooth adaptor, the standard serial console does not work and has been disabled (see `/etc/inittab` and `/boot/cmdline.txt`). You can of course [change this behaviour](https://www.raspberrypi.org/forums/viewtopic.php?t=138120) if access to the hardware serial port is important to you. 362 | > Bluetooth on the RPi3/4 also requires a custom firmware upload. This is carried out by a the `rpi3-bluetooth` OpenRC service, supplied by the `net-wireless/rpi3-bluetooth` package (see [below](#bluetooth)). 363 | 364 | * **Tip:** to connect a new Bluetooth device to your RPi3/4 (a wireless mouse or keyboard, for example), first click on the Bluetooth icon in the top toolbar. When the `Bluetooth Devices` panel opens, click on Search, and make your device discoverable (this will usually involve pressing or holding a button or switch on the device itself), shortly after which it should appear in the listing. Once it does, click on it, then press Setup..., then ensure the `Pair Device` radio button is selected, and click Next. Then, if you are attaching a more complex device such as a keyboard, you'll see a PIN code notification message displayed (simpler devices, such as mice, often don't require a PIN for pairing, in which case no message will show). If you *are* prompted with a PIN, enter the code given into your device (for a keyboard, this normally means typing it in and pressing Enter). Once the devices are paired, you'll be prompted where to connect the device to: ensure the `Human Interface Device Service (HID)` radio button is selected, and click Next. Hopefully you will then see a message telling you `Device added and connected successfully`; click Close to dismiss it. With this done, your new device should start working. However, if you want to have it connect again automatically each boot, there's one more step you need to do. Click on your new device in the list (its icon should now be showing a key symbol, indicating that it is paired), and then click on the Trust shortcut button (the one that looks like a four-pointed gold star). With this done, your device setup is complete! You can add multiple interface devices to your RPi3/4 in this manner. 365 | 366 | * The Pi uses the first (`vfat`) partition of the microSD card (`/dev/mmcblk0p1`) for booting. The various (closed-source) firmware files pre-installed there may are managed by the `sys-boot/rpi3-64bit-firmware` package (see [below](#boot_fw)). Once booted, this first partition will be mounted at `/boot`, and you may wish to check or modify the contents of the files `/boot/cmdline.txt` and `/boot/config.txt`. 367 | 368 | * Firefox is not currently provided, but *may* be in a future release. 369 | 370 | * As of Alpha1 of the image, Chromium is not provided. Chromium dropped jumbo-build support and takes days to compile. 371 | * The currently recommended browser is Falkon, a QTWebEngine based lightweight browser. 372 | 373 | * No mail client is pre-installed, but binpkgs for thunderbird and evolution should soon be available. 374 | 375 | * By default, the image uses the Pi's [VC4 GPU](https://wiki.gentoo.org/wiki/Raspberry_Pi_VC4) acceleration (VC6 in the Pi4, although it still uses the `vc4...` kernel modules) in X, which has reasonable support in the 4.19.y kernel and the supplied userspace (via `media-libs/mesa` ultimately - this has been [tweaked](https://github.com/sakaki-/genpi64-overlay/blob/a8e84d5295bd49811456a953514521ba5efa01ba/media-libs/mesa/mesa-19.1.4-r1.ebuild#L413) 376 | on the image to include v3d support for the new Pi4). Note however that this is still work in progress, so you may experience issues with certain applications. The image (as shipped) uses the mixed-mode [`vc4-fkms-v3d`](https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=159853) overlay / driver (see `/boot/config.txt`, or Applications→Settings→RPi Config Tool; you can change the driver if you wish to, or are experiencing serious glitches). On my RPi4 B at least, a `glxgears` score significantly in excess 1000fps can be obtained on an unloaded system (~400fps on a loaded desktop). Incidentally, in normal use the main load is the Xfce window manager's compositor - try turning it off to see (via Applications→Settings→Window Manager Tweaks, Compositor tab) . YMMV - if you experience problems with this setup (or find that e.g. your system is stuck on the 'rainbow square' at boot time after a kernel update), you can fall-back to the standard framebuffer mode by commenting out the `dtoverlay=vc4-fkms-v3d` line in `/boot/config.txt` (i.e., the file `config.txt` located in the microSD card's first partition). 377 | > Kodi, VLC and SMPlayer have been pre-installed on the image, and they will all make use of accelerated (Mesa/gl) playback. Because of incompatibilities and periodic crashes when using it, XVideo (xv) mode has been disabled in the X server (`/etc/X11/xorg.conf.d/50-disable-Xv.conf`); this doesn't really impinge on usability. NB: **if you find video playback framerates too slow**, it is always worth **disabling the window manager's compositor** (see point immediately above) as a first step. Hint: for some video types, SMPlayer and Kodi perform significantly better than VLC, so if you do experience 'glitchy' playback with one media player, try using one of the others. 378 | 379 | * The frequency governor is switched to `ondemand` (from the default, `powersave`), for better performance, as of version 1.0.1. This is managed by the `sys-apps/rpi3-ondemand-cpufreq` package (see [below](#ondemand)). 380 | * If you are using an RPi3 Model B board, the frequency will switch dynamically between 600MHz and 1.2GHz, depending on load. On a Model B+, it will switch between 600MHz and 1.4GHz. On an RPi4, it will switch between 600MHz and 1.5GHz. 381 | 382 | * On the RPi4, you can easily try *overclocking* your system, without voiding your warranty. To do so, open Applications→Settings→RPi Config Tool app, select the Pi4 Tuning tab, select an option from `Mid` to `Extreme` in the supplied 'manettino' ^-^, click Save and Exit, then elect to reboot when prompted. Note that you are likely to require active cooling for your RPi4 when overclocked, and it is always possible (although unlikely) that your device may fail to boot at the faster settings (if it does, simply edit the file `config.txt` on the first partition of the microSD card, comment out the `arm_freq` and `gpu_freq` settings, and try again). 383 | 384 | * On the RPi4, please make sure your EEPROM firmware is up-to-date; there is (at the time of writing) an official update available (`0137a8.bin`) that can lower power consumption by around 300mW, which makes a significant difference to this somewhat [thermally challenged](https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=245703) ^-^ device. For more details please see [this post](https://www.raspberrypi.org/forums/viewtopic.php?p=1490467#p1490467). 385 | 386 | * To login as root, modify `/etc/ssh/sshd_config` by uncommenting these lines 387 | ```shell 388 | PermitRootLogin yes 389 | PasswordAuthentication yes 390 | KbdInteractiveAuthentication yes 391 | UsePAM yes 392 | ``` 393 | This has been disabled by default, following the lead of upstream openssh to disable it. You might want to use public key encryption to connect instead to avoid needing the password. 394 | * I haven't properly tested suspend to RAM or suspend to swap functionality yet. 395 | 396 | * As of version 1.0.1, all users in the `wheel` group (which includes `demouser`) have a passwordless sudo ability for all commands. Modify `/etc/sudoers` via `visudo` to change this, if desired (the relevant line is `%wheel ALL=(ALL) NOPASSWD: ALL`). 397 | 398 | * The image uses the RPi3/4's hardware random number generator to feed `/dev/random` (via `sys-apps/rng-tools`); see [these notes](https://github.com/sakaki-/genpi64-overlay/tree/master/sys-boot/rpi3-64bit-firmware) for further details. 399 | 400 | * As a (limited, 64-bit) build of `media-libs/raspberrypi-userland` is included, you can use `vcgencmd` etc. As of version 1.5.2 of the image, this includes support for MMAL (including bundled tools such as `raspivid` and `raspicam`), although OpenMAX-IL is not yet supported from a 64-bit userland. 401 | 402 | * If you wish to share files on a network with Windows boxes, please note that `net-fs/samba` is bundled as of version 1.2.2 of the image. To configure and activate it, please see e.g. [these notes](https://forums.gentoo.org/viewtopic-p-8215174.html#8215174). 403 | 404 | * An `sysctl.d` rule (`35-low-memory-cache-settings.conf`) is used to modify the kernel cache settings slightly, for better performance in a memory constrained environment, per [these notes](https://www.codero.com/knowledge-base/pdf.php?cat=3&id=388&artlang=en). 405 | 406 | * You can easily install (and run) 32-bit Raspbian apps on your 64-bit Gentoo system if you like (using `apt-get` from a `chroot`), since [ARMv8 supports mixed-mode userland](https://community.arm.com/processors/f/discussions/3330/how-aarch32-bit-applications-will-be-supported-on-aarch64?ReplyFilter=Answers&ReplySortBy=Answers&ReplySortOrder=Descending). If this interests you, please see my wiki entry on this subject, [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Running-32-bit-Raspbian-Packages-on-your-64-bit-Gentoo-System). 407 | 408 | * To install source packages with resource-intensive build profiles, you can temporarily mount the image within a `binfmt_misc` QEMU user-mode `chroot` on your PC, and perform the `emerge` there. For further details, please see my wiki tutorial [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Build-aarch64-Packages-on-your-PC%2C-with-User-Mode-QEMU-and-binfmt_misc). 409 | 410 | * If you would like to run **benchmarks** on your RPi3/4 system, please see [these notes](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Effective-Benchmarking-on-your-64-Bit-RPi-System). 411 | 412 | * You can easily remove unwanted applications, and even the Xfce4 graphical desktop itself, from your 64-bit Gentoo system if desired. To do so, please refer to my notes [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Create-a-Slimmed-Down-Version-of-the-Image). 413 | 414 | * If you'd like to set up a persistent dual-monitor setup on an RPi4, please see my short tutorial on this project's open wiki [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Set-Up-Dual-Displays-on-your-RPi4) (also contains some notes useful for single-display systems too). 415 | 416 | ## Maintenance Notes (Advanced Users Only) (↓[skip](#miscpoints)) 417 | 418 | The following are some notes regarding optional maintenance tasks. The topics here may be of interest to advanced users, but it is not necessary to read these to use the image day-to-day. 419 | 420 | ### Have your Gentoo PC Do the Heavy Lifting! 421 | 422 | The RPi3 (and even the RPi4, although significantly better) does not have a particularly fast processor when compared to a modern PC. While this is fine when running the device in day-to-day mode (as a IME-free lightweight desktop replacement, for example), it does pose a bit of an issue when building large packages from source. 423 | > Of course, as the (>= 1.1.0) image now has a weekly-autobuild [binhost](#binhost) provided, this will only really happen if you start setting custom USE flags on packages like `app-office/libreoffice`, or emerging lots of packages not on the [original pre-installed set](https://github.com/sakaki-/gentoo-on-rpi-64bit/blob/master/reference/world-all-packages). 424 | 425 | However, there is a solution to this, and it is not as scary as it sounds - leverage the power of your PC (assuming it too is running Gentoo Linux) as a cross-compilation host! 426 | 427 | For example, you can cross-compile kernels for your RPi3/4 on your PC very quickly (around 5-15 minutes from scratch), by using Gentoo's `crossdev` tool. See my full instructions [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Set-Up-Your-Gentoo-PC-for-Cross-Compilation-with-crossdev), [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Build-an-RPi4-64bit-Kernel-on-your-crossdev-PC) and [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Build-an-RPi3-64bit-Kernel-on-your-crossdev-PC) on this project's open [wiki](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki). 428 | 429 | Should you setup `crossdev` on your PC in this manner, you can then take things a step further, by leveraging your PC as a `distcc` server (instructions [here](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Set-Up-Your-crossdev-PC-for-Distributed-Compilation-with-distcc) on the wiki). Then, with just some simple configuration changes on your RPi3 (see [these notes](https://github.com/sakaki-/gentoo-on-rpi-64bit/wiki/Set-Up-Your-RPi3-as-a-distcc-Client)), you can distribute C/C++ compilation (and header preprocessing) to your remote machine, which makes system updates a lot quicker (and the provided tool `genup` will automatically take advantage of this distributed compilation ability, if available). 430 | 431 | > Since they share the same ARMv8a architecture (`march`), binaries built in this manner can be used on either a RPi3 Model B, B+ *or* an RPi4 Model B, without modification. 432 | 433 | ### Using your RPi3/4 as a Headless Server 434 | 435 | If you want to run a dedicated server program on your RPi3 or RPi4 (for example, a cryptocurrency miner), you won't generally want (or need) the graphical desktop user interface. To disable it, issue (as root): 436 | ```console 437 | pi64 ~ # rc-update del xdm default 438 | ``` 439 | 440 | You can also reclaim the memory reserved for the `vc4` graphics driver (this is optional). To do so, issue: 441 | ```console 442 | pi64 ~ # nano -w /boot/config.txt 443 | ``` 444 | 445 | and comment out the following line, so it reads: 446 | ```ini 447 | #dtoverlay=vc4-fkms-v3d 448 | ``` 449 | 450 | (Your setup may have a `cma` specification following the `vc4-fkms-v3d`; it's still the same line, and should be commented.) 451 | 452 | Also ensure that the camera module support software is not loaded, and that only a minimal amount of GPU memory is allocated - to do so, ensure the below lines in the file read as follows: 453 | ```ini 454 | #start_x=1 455 | gpu_mem=16 456 | ``` 457 | 458 | Leave the rest of the file as-is. Save, and exit `nano`. 459 | 460 | Reboot your system. You will now have a standard terminal login available only, which greatly saves on system resources. 461 | 462 | It is generally more reliable to use the Ethernet rather than the WiFi network interface when running a headless server in this manner. Also, make sure your system has an adequate heatsink fitted (or even active CPU cooling, for particularly demanding applications), since the RPi3 (particuarly when running in 64-bit mode) can [get quite hot](https://www.theregister.co.uk/2017/10/18/active_cooling_a_raspberry_pi_3/), leading to thermal throttling or even protective system shutdown if your cooling is insufficient. The RPi3 Model B+ has a [integral heat-spreader](https://core-electronics.com.au/tutorials/raspberry-pi-3-model-b-plus-performance-vs-3-model-b.html), so (in addition to having a higher clock speed) it may be a somewhat better choice than the RPi3 Model B for more demanding applications. The RPi4 has [even more significant thermal challenges](https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=245703) than the RPi3, so active cooling is recommended for demanding applications. 463 | 464 | > Of course, take the normal precautions when running an internet-exposed server in this manner: for example, set up an appropriate firewall, consider running the server process under `firejail`, modify the shipped-default passwords, and keep your system up-to-date by (manually) running `genup`, from time to time. 465 | 466 | Should you wish to revert back to using the graphical desktop at some point in the future, simply issue (as root): 467 | ```console 468 | pi64 ~ # rc-update add xdm default 469 | ``` 470 | 471 | Then, if you edited `/boot/config.txt` [above](#reclaim_mem), undo that change now. Issue: 472 | ```console 473 | pi64 ~ # nano -w /boot/config.txt 474 | ``` 475 | 476 | and uncomment the following line, so it reads: 477 | ```ini 478 | dtoverlay=vc4-fkms-v3d 479 | ``` 480 | 481 | > With modern boot firmware, the recommendation is *not* to set an explicit `cma` parameter on `vc4-fkms-v3d`. 482 | 483 | If you wish to use the camera, and hardware video codecs, also ensure that the below lines read as follows (if not, this step may be omitted): 484 | ```ini 485 | start_x=1 486 | gpu_mem=128 487 | ``` 488 | 489 | Leave the rest of the file as-is. Save, and exit `nano`. Reboot your system, and you should have your full graphical desktop back again! 490 | 491 | 492 | ## Miscellaneous Points (Advanced Users Only) (↓[skip](#helpwanted)) 493 | 494 | The following are some notes about the detailed structure of the image. It is not necessary to read these to use the image day-to-day. 495 | 496 | ### Subscribed Ebuild Repositories (_aka_ Overlays) 497 | 498 | The image is subscribed to the following ebuild repositories: 499 | * **gentoo**: this is the main Gentoo tree of course, but is (by default) supplied via `rsync://isshoni.org/gentoo-portage-pi64-gem`, a weekly-gated, signature-authenticated portage rsync mirror locked to the binhost's available files, as described [above](#rsync). 500 | * **[genpi-tools](https://github.com/GenPi64/genpi-tools)**: this provides a number of small utilities for Gentoo. The image currently uses the following ebuilds from the `genpi-tools` overlay: 501 | * **app-portage/showem** [source](https://github.com/GenPi64/showem), [manpage](https://github.com/GenPi64/gentoo-on-rpi-64bit/blob/master/reference/showem.pdf) 502 | 503 | A tool to view the progress of parallel `emerge` operations. 504 | * **app-portage/genup** [source](https://github.com/GenPi64/genup), [manpage](https://github.com/GenPi64/gentoo-on-rpi-64bit/blob/master/reference/genup.pdf) 505 | 506 | * **[genpi64](https://github.com/GenPi64/genpi64-overlay)**: this overlay (which used to be named `rpi3` and was subsequently [migrated](https://forums.gentoo.org/viewtopic-p-8362116.html#8362116) at v1.5.0 with the advent of RPi4 support) provides ebuilds specific to the Raspberry Pi 3 & Pi 4, or builds that have fallen off the main Gentoo tree but which are the last known reliable variants for `arm64`. It also provides the [custom profile](#profile) [`genpi64:default/linux/arm64/17.0/desktop/genpi64`](hhttps://github.com/GenPi64/genpi64-overlay/tree/master/profiles/targets/genpi64). A list of provided ebuilds may be found on the [overlay's project page](https://github.com/GenPi64/genpi64-overlay#list_of_ebuilds). 507 | 508 | ## Project Wiki 509 | 510 | In addition to the notes in this README, this project also has an associated open **wiki**, containing a number of short tutorial articles you may find helpful when using 64-bit Gentoo on your RPi3 or RPi4. 511 | 512 | You can view the wiki homepage [here](https://github.com/GenPi64/gentoo-on-rpi-64bit/wiki). Feel free to add your own material! 513 | 514 | ## Help Wanted! 515 | 516 | You've got this far through the README - I'm impressed ^-^. In fact, you may be just the sort of person to help get `arm64` into a more stable state in the main Gentoo tree... 517 | 518 | ## Acknowledgement 519 | 520 | I'd like to acknowledge NeddySeagoon's work getting Gentoo to run in 64-bit mode on the RPi3 (see particularly [this thread](https://forums.gentoo.org/viewtopic-t-1041352.html), which was a really useful reference when putting this project together originally). 521 | 522 | ## Feedback Welcome! 523 | 524 | If you have any problems, questions or comments regarding this project, please either use our Discord, or try to get in touch with us on IRC (#gentoo-arm, Freenode). 525 | 526 | 527 | -------------------------------------------------------------------------------- /licenses/Broadcom: -------------------------------------------------------------------------------- 1 | 2 | SOFTWARE LICENSE AGREEMENT 3 | 4 | Unless you and Broadcom Corporation (“Broadcom”) execute a separate written software license agreement governing use of the accompanying software, this software is licensed to you under the terms of this Software License Agreement (“Agreement”). 5 | 6 | ANY USE, REPRODUCTION OR DISTRIBUTION OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS AGREEMENT. 7 | 8 | 1. DEFINITIONS. 9 | 10 | 1.1. “Broadcom Product” means any of the proprietary integrated circuit product(s) sold by Broadcom with which the Software was designed to be used, or their successors. 11 | 12 | 1.2. “Licensee” means you or if you are accepting on behalf of an entity then the entity and its affiliates exercising rights under, and complying with all of the terms of this Agreement. 13 | 14 | 1.3. “Software” shall mean that software made available by Broadcom to Licensee in binary code form with this Agreement. 15 | 16 | 2. LICENSE GRANT; OWNERSHIP 17 | 18 | 2.1. License Grants. Subject to the terms and conditions of this Agreement, Broadcom hereby grants to Licensee a non-exclusive, non-transferable, royalty-free license (i) to use and integrate the Software in conjunction with any other software; and (ii) to reproduce and distribute the Software complete, unmodified and only for use with a Broadcom Product. 19 | 20 | 2.2. Restriction on Modification. If and to the extent that the Software is designed to be compliant with any published communications standard (including, without limitation, DOCSIS, HomePNA, IEEE, and ITU standards), Licensee may not make any modifications to the Software that would cause the Software or the accompanying Broadcom Products to be incompatible with such standard. 21 | 22 | 2.3. Restriction on Distribution. Licensee shall only distribute the Software (a) under the terms of this Agreement and a copy of this Agreement accompanies such distribution, and (b) agrees to defend and indemnify Broadcom and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Software by the Licensee except as contemplated herein. 23 | 24 | 2.4. Proprietary Notices. Licensee shall not remove, efface or obscure any copyright or trademark notices from the Software. Licensee shall include reproductions of the Broadcom copyright notice with each copy of the Software, except where such Software is embedded in a manner not readily accessible to the end user. Licensee acknowledges that any symbols, trademarks, tradenames, and service marks adopted by Broadcom to identify the Software belong to Broadcom and that Licensee shall have no rights therein. 25 | 26 | 2.5. Ownership. Broadcom shall retain all right, title and interest, including all intellectual property rights, in and to the Software. Licensee hereby covenants that it will not assert any claim that the Software created by or for Broadcom infringe any intellectual property right owned or controlled by Licensee. 27 | 28 | 2.6. No Other Rights Granted; Restrictions. Apart from the license rights expressly set forth in this Agreement, Broadcom does not grant and Licensee does not receive any ownership right, title or interest nor any security interest or other interest in any intellectual property rights relating to the Software, nor in any copy of any part of the foregoing. Licensee shall not (i) use, license, sell or otherwise distribute the Software except as provided in this Agreement, (ii) attempt to reverse engineer, decompile or disassemble any portion of the Software; or (iii) use the Software or other material in violation of any applicable law or regulation, including but not limited to any regulatory agency, such as FCC, rules. 29 | 30 | 3. NO WARRANTY OR SUPPORT 31 | 32 | 3.1. No Warranty. THE SOFTWARE IS OFFERED “AS IS,” AND BROADCOM GRANTS AND LICENSEE RECEIVES NO WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, BY STATUTE, COMMUNICATION OR CONDUCT WITH LICENSEE, OR OTHERWISE. BROADCOM SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A SPECIFIC PURPOSE OR NONINFRINGEMENT CONCERNING THE SOFTWARE OR ANY UPGRADES TO OR DOCUMENTATION FOR THE SOFTWARE. WITHOUT LIMITATION OF THE ABOVE, BROADCOM GRANTS NO WARRANTY THAT THE SOFTWARE IS ERROR-FREE OR WILL OPERATE WITHOUT INTERRUPTION, AND GRANTS NO WARRANTY REGARDING ITS USE OR THE RESULTS THEREFROM INCLUDING, WITHOUT LIMITATION, ITS CORRECTNESS, ACCURACY OR RELIABILITY. 33 | 34 | 3.2. No Support. Nothing in this agreement shall obligate Broadcom to provide any support for the Software. Broadcom may, but shall be under no obligation to, correct any defects in the Software and/or provide updates to licensees of the Software. Licensee shall make reasonable efforts to promptly report to Broadcom any defects it finds in the Software, as an aid to creating improved revisions of the Software. 35 | 36 | 3.3. Dangerous Applications. The Software is not designed, intended, or certified for use in components of systems intended for the operation of weapons, weapons systems, nuclear installations, means of mass transportation, aviation, life-support computers or equipment (including resuscitation equipment and surgical implants), pollution control, hazardous substances management, or for any other dangerous application in which the failure of the Software could create a situation where personal injury or death may occur. Licensee understands that use of the Software in such applications is fully at the risk of Licensee. 37 | 38 | 4. TERM AND TERMINATION 39 | 40 | 4.1. Termination. This Agreement will automatically terminate if Licensee fails to comply with any of the terms and conditions hereof. In such event, Licensee must destroy all copies of the Software and all of its component parts. 41 | 42 | 4.2. Effect Of Termination. Upon any termination of this Agreement, the rights and licenses granted to Licensee under this Agreement shall immediately terminate. 43 | 44 | 4.3. Survival. The rights and obligations under this Agreement which by their nature should survive termination will remain in effect after expiration or termination of this Agreement. 45 | 46 | 5. CONFIDENTIALITY 47 | 48 | 5.1. Obligations. Licensee acknowledges and agrees that any documentation relating to the Software, and any other information (if such other information is identified as confidential or should be recognized as confidential under the circumstances) provided to Licensee by Broadcom hereunder (collectively, “Confidential Information”) constitute the confidential and proprietary information of Broadcom, and that Licensee’s protection thereof is an essential condition to Licensee’s use and possession of the Software. Licensee shall retain all Confidential Information in strict confidence and not disclose it to any third party or use it in any way except under a written agreement with terms and conditions at least as protective as the terms of this Section. Licensee will exercise at least the same amount of diligence in preserving the secrecy of the Confidential Information as it uses in preserving the secrecy of its own most valuable confidential information, but in no event less than reasonable diligence. Information shall not be considered Confidential Information if and to the extent that it: (i) was in the public domain at the time it was disclosed or has entered the public domain through no fault of Licensee; (ii) was known to Licensee, without restriction, at the time of disclosure as proven by the files of Licensee in existence at the time of disclosure; or (iii) becomes known to Licensee, without restriction, from a source other than Broadcom without breach of this Agreement by Licensee and otherwise not in violation of Broadcom’s rights. 49 | 50 | 5.2. Return of Confidential Information. Notwithstanding the foregoing, all documents and other tangible objects containing or representing Broadcom Confidential Information and all copies thereof which are in the possession of Licensee shall be and remain the property of Broadcom, and shall be promptly returned to Broadcom upon written request by Broadcom or upon termination of this Agreement. 51 | 52 | 6. LIMITATION OF LIABILITY 53 | TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL BROADCOM OR ANY OF BROADCOM’S LICENSORS HAVE ANY LIABILITY FOR ANY INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER FOR BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE, ARISING OUT OF THIS AGREEMENT, INCLUDING BUT NOT LIMITED TO LOSS OF PROFITS, EVEN IF SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Broadcom’s liability whether in contract, tort (including negligence), or otherwise, exceed the amount paid by Licensee for Software under this Agreement. THESE LIMITATIONS SHALL APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY. 54 | 55 | 7. MISCELLANEOUS 56 | 57 | 7.1. Assignment. This Agreement shall be binding upon and inure to the benefit of the parties and their respective successors and assigns, provided, however that Licensee may not assign this Agreement or any rights or obligation hereunder, directly or indirectly, by operation of law or otherwise, without the prior written consent of Broadcom, and any such attempted assignment shall be void. Notwithstanding the foregoing, Licensee may assign this Agreement to a successor to all or substantially all of its business or assets to which this Agreement relates that is not a competitor of Broadcom. 58 | 59 | 7.2. Governing Law; Venue. This Agreement shall be governed by the laws of California without regard to any conflict-of-laws rules, and the United Nations Convention on Contracts for the International Sale of Goods is hereby excluded. The sole jurisdiction and venue for actions related to the subject matter hereof shall be the state and federal courts located in the County of Orange, California, and both parties hereby consent to such jurisdiction and venue. 60 | 61 | 7.3. Severability. All terms and provisions of this Agreement shall, if possible, be construed in a manner which makes them valid, but in the event any term or provision of this Agreement is found by a court of competent jurisdiction to be illegal or unenforceable, the validity or enforceability of the remainder of this Agreement shall not be affected if the illegal or unenforceable provision does not materially affect the intent of this Agreement. If the illegal or unenforceable provision materially affects the intent of the parties to this Agreement, this Agreement shall become terminated. 62 | 63 | 7.4. Equitable Relief. Licensee hereby acknowledges that its breach of this Agreement would cause irreparable harm and significant injury to Broadcom that may be difficult to ascertain and that a remedy at law would be inadequate. Accordingly, Licensee agrees that Broadcom shall have the right to seek and obtain immediate injunctive relief to enforce obligations under the Agreement in addition to any other rights and remedies it may have. 64 | 65 | 7.5. Export Regulations. The parties agree that they shall each comply, at their own expense, with the U.S. Foreign Corrupt Practices Act and all import and export laws, restrictions, national security controls and regulations of the United States and any applicable foreign agency or authority. The parties shall not import, export or re-export, or authorize the export or re-export of the Software or any other product, technology, or information that it obtains or learns hereunder, or any copy or direct product thereof, in violation of any of such laws, restrictions, or regulations or without any license or approval required thereunder. Any and all obligations of the parties to provide the Software or any other product, technology, or information hereunder shall be subject in all respects to such laws, restrictions, and regulations. 66 | 67 | 7.6. Waiver. The waiver of, or failure to enforce, any breach or default hereunder shall not constitute the waiver of any other or subsequent breach or default. 68 | 69 | 7.7. Entire Agreement. This Agreement sets forth the entire Agreement between the parties and supersedes any and all prior proposals, agreements and representations between them, whether written or oral concerning the Software. This Agreement may be changed only by mutual agreement of the parties in writing. 70 | -------------------------------------------------------------------------------- /licenses/CC-Sampling-Plus-1.0: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | Sampling Plus 1.0 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS LICENSE DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR 10 | DAMAGES RESULTING FROM ITS USE. 11 | 12 | License 13 | 14 | THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE 15 | COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY 16 | COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS 17 | AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED. 18 | 19 | BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE 20 | TO BE BOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE 21 | RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS 22 | AND CONDITIONS. 23 | 24 | 1. Definitions 25 | 26 | a. "Collective Work" means a work, such as a periodical issue, anthology 27 | or encyclopedia, in which the Work in its entirety in unmodified form, 28 | along with a number of other contributions, constituting separate and 29 | independent works in themselves, are assembled into a collective 30 | whole. A work that constitutes a Collective Work will not be 31 | considered a Derivative Work (as defined below) for the purposes of 32 | this License. 33 | b. "Derivative Work" means a work based upon the Work or upon the Work 34 | and other pre-existing works, such as a translation, musical 35 | arrangement, dramatization, fictionalization, motion picture version, 36 | sound recording, art reproduction, abridgment, condensation, or any 37 | other form in which the Work may be recast, transformed, or adapted, 38 | except that a work that constitutes a Collective Work will not be 39 | considered a Derivative Work for the purpose of this License. 40 | c. "Licensor" means the individual or entity that offers the Work under 41 | the terms of this License. 42 | d. "Original Author" means the individual or entity who created the Work. 43 | e. "Work" means the copyrightable work of authorship offered under the 44 | terms of this License. 45 | f. "You" means an individual or entity exercising rights under this 46 | License who has not previously violated the terms of this License with 47 | respect to the Work, or who has received express permission from the 48 | Licensor to exercise rights under this License despite a previous 49 | violation. 50 | 51 | 2. Fair Use Rights. Nothing in this license is intended to reduce, limit, 52 | or restrict any rights arising from fair use, first sale or other 53 | limitations on the exclusive rights of the copyright owner under copyright 54 | law or other applicable laws. 55 | 56 | 3. License Grant & Restrictions. Subject to the terms and conditions of 57 | this License, Licensor hereby grants You a worldwide, royalty-free, non- 58 | exclusive, perpetual (for the duration of the applicable copyright) 59 | license to exercise the rights in the Work as stated below on the 60 | conditions as stated below: 61 | 62 | a. Re-creativity permitted. You may create and reproduce Derivative 63 | Works, provided that: 64 | 65 | i. the Derivative Work(s) constitute a good-faith partial or 66 | recombined usage employing "sampling," "collage," "mash-up," or 67 | other comparable artistic technique, whether now known or 68 | hereafter devised, that is highly transformative of the original, 69 | as appropriate to the medium, genre, and market niche; and 70 | ii. Your Derivative Work(s) must only make a partial use of the 71 | original Work, or if You choose to use the original Work as a 72 | whole, You must either use the Work as an insubstantial portion 73 | of Your Derivative Work(s) or transform it into something 74 | substantially different from the original Work. In the case of a 75 | musical Work and/or audio recording, the mere synchronization 76 | ("synching") of the Work with a moving image shall not be 77 | considered a transformation of the Work into something 78 | substantially different. 79 | 80 | b. You may distribute copies or phonorecords of, display publicly, 81 | perform publicly, and perform publicly by means of a digital audio 82 | transmission, any Derivative Work(s) authorized under this License. 83 | c. Prohibition on advertising. All advertising and promotional uses are 84 | excluded from the above rights, except for advertisement and promotion 85 | of the Derivative Work(s) that You are creating from the Work and 86 | Yourself as the author thereof. 87 | d. Noncommercial sharing of verbatim copies permitted. 88 | 89 | i. You may reproduce the Work, incorporate the Work into one or more 90 | Collective Works, and reproduce the Work as incorporated in the 91 | Collective Works. You may distribute copies or phonorecords of, 92 | display publicly, perform publicly, and perform publicly by means 93 | of a digital audio transmission the Work including or incorporated 94 | in Collective Works. 95 | ii. You may not exercise any of the rights granted to You in the 96 | paragraph immediately above in any manner that is primarily 97 | intended for or directed toward commercial advantage or private 98 | monetary compensation. The exchange of the Work for other 99 | copyrighted works by means of digital file-sharing or otherwise 100 | shall not be considered to be intended for or directed toward 101 | commercial advantage or private monetary compensation, provided 102 | there is no payment of any monetary compensation in connection 103 | with the exchange of copyrighted works. 104 | 105 | e. Attribution and Notice. 106 | 107 | i. If You distribute, publicly display, publicly perform, or publicly 108 | digitally perform the Work or any Derivative Works or Collective 109 | Works, You must keep intact all copyright notices for the Work and 110 | give the Original Author credit reasonable to the medium or means 111 | You are utilizing by conveying the name (or pseudonym if 112 | applicable) of the Original Author if supplied; the title of the 113 | Work if supplied; to the extent reasonably practicable, provide 114 | the Uniform Resource Identifier, if any, that Licensor specifies 115 | to be associated with the Work or a Derivative Work, unless such 116 | Uniform Resource Identifier does not refer to the copyright notice 117 | or licensing information for the Work; and in the case of a 118 | Derivative Work, provide a credit identifying the use of the Work 119 | in the Derivative Work (e.g., "Remix of the Work by Original 120 | Author," or "Inclusion of a portion of the Work by Original Author 121 | in collage"). Such credit may be implemented in any reasonable 122 | manner; provided, however, that in the case of a Derivative Work 123 | or Collective Work, at a minimum such credit will appear where any 124 | other comparable authorship credit appears and in a manner at 125 | least as prominent as such other comparable authorship credit. 126 | ii. You may distribute, publicly display, publicly perform or publicly 127 | digitally perform the Work only under the terms of this License, 128 | and You must include a copy of, or the Uniform Resource Identifier 129 | for, this License with every copy or phonorecord of the Work or 130 | Derivative Work You distribute, publicly display, publicly 131 | perform, or publicly digitally perform. You may not offer or 132 | impose any terms on the Work that alter or restrict the terms of 133 | this License or the recipients' exercise of the rights granted 134 | hereunder. You may not sublicense the Work. You must keep intact 135 | all notices that refer to this License and to the disclaimer of 136 | warranties. You may not distribute, publicly display, publicly 137 | perform, or publicly digitally perform the Work with any 138 | technological measures that control access of use of the Work in a 139 | manner inconsistent with the terms of this License. The above 140 | applies to the Work as incorporated in a Collective Work, but this 141 | does not require the Collective Work apart from the Work itself to 142 | be made subject to the terms of this License. Upon notice from any 143 | Licensor You must, to the extent practicable, remove from the 144 | Derivative Work or Collective Work any reference to such Licensor 145 | or the Original Author, as requested. 146 | 147 | The above rights may be exercised in all media and formats whether now 148 | known or hereafter devised. The above rights include the right to make 149 | such modifications as are technically necessary to exercise the rights in 150 | other media and formats. All rights not expressly granted by Licensor are 151 | hereby reserved. 152 | 153 | 4. Disclaimer 154 | 155 | UNLESS SPECIFIED OTHERWISE BY THE PARTIES IN A SEPARATE WRITING, LICENSOR 156 | OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS 157 | OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, 158 | MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE 159 | ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE 160 | OF ERRORS, WHETHER OR NOT DISCOVERABLE. 161 | 162 | 5. Limitation on Liability. 163 | 164 | IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY 165 | SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING 166 | OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN 167 | ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 168 | 169 | 6. Termination 170 | 171 | a. This License and the rights granted hereunder will terminate 172 | automatically upon any breach by You of the terms of this License. 173 | Individuals or entities who have received Derivative Works or 174 | Collective Works from You under this License, however, will not have 175 | their licenses terminated provided such individuals or entities remain 176 | in full compliance with those licenses. Sections 1, 2, 4, 5, 6, and 7 177 | will survive any termination of this License. 178 | b. Subject to the above terms and conditions, the license granted here is 179 | perpetual (for the duration of the applicable copyright in the Work). 180 | Notwithstanding the above, Licensor reserves the right to release the 181 | Work under different license terms or to stop distributing the Work at 182 | any time; provided, however that any such election will not serve to 183 | withdraw this License (or any other license that has been granted 184 | under the terms of this License), and this License will continue in 185 | full force and effect unless terminated as stated above. 186 | 187 | 7. Miscellaneous 188 | 189 | a. Each time You distribute or publicly digitally perform the Work or a 190 | Collective Work, the Licensor offers to the recipient a license to the 191 | Work on the same terms and conditions as the license granted to You 192 | under this License. 193 | b. Each time You distribute or publicly digitally perform a Derivative 194 | Work, Licensor offers to the recipient a license to the original Work 195 | on the same terms and conditions as the license granted to You under 196 | this License. 197 | c. If any provision of this License is invalid or unenforceable under 198 | applicable law, it shall not affect the validity or enforceability of 199 | the remainder of the terms of this License, and without further action 200 | by the parties to this agreement, such provision shall be reformed to 201 | the minimum extent necessary to make such provision valid and 202 | enforceable. 203 | d. No term or provision of this License shall be deemed waived and no 204 | breach consented to unless such waiver or consent shall be in writing 205 | and signed by the party to be charged with such waiver or consent. 206 | e. This License constitutes the entire agreement between the parties with 207 | respect to the Work licensed here. There are no understandings, 208 | agreements, or representations with respect to the Work, and with 209 | respect to the subject matter hereof, not specified above. Licensor 210 | shall not be bound by any additional provisions that may appear in any 211 | communication from You. This License may not be modified without the 212 | mutual written agreement of the Licensor and You. 213 | -------------------------------------------------------------------------------- /licenses/LICENCE.broadcom-rpi-boot: -------------------------------------------------------------------------------- 1 | Copyright (c) 2006, Broadcom Corporation. 2 | Copyright (c) 2015, Raspberry Pi (Trading) Ltd 3 | All rights reserved. 4 | 5 | Redistribution. Redistribution and use in binary form, without 6 | modification, are permitted provided that the following conditions are 7 | met: 8 | 9 | * This software may only be used for the purposes of developing for, 10 | running or using a Raspberry Pi device. 11 | * Redistributions must reproduce the above copyright notice and the 12 | following disclaimer in the documentation and/or other materials 13 | provided with the distribution. 14 | * Neither the name of Broadcom Corporation nor the names of its suppliers 15 | may be used to endorse or promote products derived from this software 16 | without specific prior written permission. 17 | 18 | DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 19 | CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, 20 | BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND 21 | FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 22 | COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 23 | INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 24 | BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS 25 | OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND 26 | ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR 27 | TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE 28 | USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH 29 | DAMAGE. 30 | 31 | -------------------------------------------------------------------------------- /licenses/LICENCE.broadcom_bcm43xx: -------------------------------------------------------------------------------- 1 | SOFTWARE LICENSE AGREEMENT 2 | 3 | The accompanying software in binary code form (“Software”), is licensed to you, 4 | or, if you are accepting on behalf of an entity, the entity and its affiliates 5 | exercising rights hereunder (“Licensee”) subject to the terms of this software 6 | license agreement (“Agreement”), unless Licensee and Broadcom Corporation 7 | (“Broadcom”) execute a separate written software license agreement governing 8 | use of the Software. ANY USE, REPRODUCTION, OR DISTRIBUTION OF THE SOFTWARE 9 | CONSTITUTES LICENSEE’S ACCEPTANCE OF THIS AGREEMENT. 10 | 11 | 1. License. Subject to the terms and conditions of this Agreement, 12 | Broadcom hereby grants to Licensee a limited, non-exclusive, non-transferable, 13 | royalty-free license: (i) to use and integrate the Software with any other 14 | software; and (ii) to reproduce and distribute the Software complete, 15 | unmodified, and as provided by Broadcom, solely for use with Broadcom 16 | proprietary integrated circuit product(s) sold by Broadcom with which the 17 | Software was designed to be used, or their successors. 18 | 19 | 2. Restrictions. Licensee shall distribute Software with a copy of this 20 | Agreement. Licensee shall not remove, efface or obscure any copyright or 21 | trademark notices from the Software. Reproductions of the Broadcom copyright 22 | notice shall be included with each copy of the Software, except where such 23 | Software is embedded in a manner not readily accessible to the end user. 24 | Licensee shall not: (i) use, license, sell or otherwise distribute the Software 25 | except as provided in this Agreement; (ii) attempt to modify in any way, 26 | reverse engineer, decompile or disassemble any portion of the Software; or 27 | (iii) use the Software or other material in violation of any applicable law or 28 | regulation, including but not limited to any regulatory agency. This Agreement 29 | shall automatically terminate upon Licensee’s failure to comply with any of the 30 | terms of this Agreement. In such event, Licensee will destroy all copies of the 31 | Software and its component parts. 32 | 33 | 3. Ownership. The Software is licensed and not sold. Title to and 34 | ownership of the Software, including all intellectual property rights thereto, 35 | and any portion thereof remain with Broadcom or its licensors. Licensee hereby 36 | covenants that it will not assert any claim that the Software created by or for 37 | Broadcom infringe any intellectual property right owned or controlled by 38 | Licensee. 39 | 40 | 4. Disclaimer. THE SOFTWARE IS OFFERED “AS IS,” AND BROADCOM PROVIDES AND 41 | GRANTS AND LICENSEE RECEIVES NO SUPPORT AND NO WARRANTIES OF ANY KIND, EXPRESS 42 | OR IMPLIED, BY STATUTE, COMMUNICATION OR CONDUCT WITH LICENSEE, OR OTHERWISE. 43 | BROADCOM SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY, 44 | FITNESS FOR A SPECIFIC PURPOSE, OR NONINFRINGEMENT CONCERNING THE SOFTWARE OR 45 | ANY UPGRADES TO OR DOCUMENTATION FOR THE SOFTWARE. WITHOUT LIMITATION OF THE 46 | ABOVE, BROADCOM GRANTS NO WARRANTY THAT THE SOFTWARE IS ERROR-FREE OR WILL 47 | OPERATE WITHOUT INTERRUPTION, AND GRANTS NO WARRANTY REGARDING ITS USE OR THE 48 | RESULTS THEREFROM INCLUDING, WITHOUT LIMITATION, ITS CORRECTNESS, ACCURACY, OR 49 | RELIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL BROADCOM 50 | OR ANY OF ITS LICENSORS HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, 51 | INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND ON ANY THEORY 52 | OF LIABILITY, WHETHER FOR BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE) OR 53 | OTHERWISE, ARISING OUT OF THIS AGREEMENT OR USE, REPRODUCTION, OR DISTRIBUTION 54 | OF THE SOFTWARE, INCLUDING BUT NOT LIMITED TO LOSS OF DATA AND LOSS OF PROFITS, 55 | EVEN IF SUCH PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THESE 56 | LIMITATIONS SHALL APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY 57 | LIMITED REMEDY. 58 | 59 | 5. Export Laws. LICENSEE UNDERSTANDS AND AGREES THAT THE SOFTWARE IS 60 | SUBJECT TO UNITED STATES AND OTHER APPLICABLE EXPORT-RELATED LAWS AND 61 | REGULATIONS AND THAT LICENSEE MAY NOT EXPORT, RE-EXPORT OR TRANSFER THE 62 | SOFTWARE OR ANY DIRECT PRODUCT OF THE SOFTWARE EXCEPT AS PERMITTED UNDER THOSE 63 | LAWS. WITHOUT LIMITING THE FOREGOING, EXPORT, RE-EXPORT, OR TRANSFER OF THE 64 | SOFTWARE TO CUBA, IRAN, NORTH KOREA, SUDAN, AND SYRIA IS PROHIBITED. 65 | 66 | -------------------------------------------------------------------------------- /licenses/bluez-firmware: -------------------------------------------------------------------------------- 1 | http://packages.debian.org/changelogs/pool/non-free/b/bluez-firmware/current/copyright 2 | 3 | The BlueZ project has permission from Broadcom Corporation to 4 | distribute this firmware, as long as the notice contained in 5 | broadcom/BCM-LEGAL.txt accompanies the firmware. 6 | 7 | This arrangement was made with BlueZ author Max Krasnyansky 8 | . 9 | 10 | BCM-LEGAL.txt content: 11 | 12 | BCM firmware version 2.16 13 | Copyright (c) 2000-2003 Broadcom Corporation 14 | 15 | Contact info: 16 | bluetooth_help@broadcom.com 17 | -------------------------------------------------------------------------------- /licenses/freedist: -------------------------------------------------------------------------------- 1 | Freely Distributable. 2 | -------------------------------------------------------------------------------- /licenses/linux-firmware: -------------------------------------------------------------------------------- 1 | Gentoo license note: 2 | 3 | Linux firmware images are distributed under a variety of licenses, 4 | many of them being non-free. Most likely, upstream redistribution of 5 | some firmware images may conflict with the licenses or lack thereof on 6 | the images. You will need to check the WHENCE and LICEN[CS]E.* files 7 | in the package for specific licensing terms. 8 | -------------------------------------------------------------------------------- /licenses/linux-fw-redistributable: -------------------------------------------------------------------------------- 1 | Gentoo license note: 2 | 3 | Linux firmware images are distributed under a variety of licenses, 4 | many of them being non-free. However, all images whose license is 5 | subsumed under this license label should at least be redistributable. 6 | You will need to check the WHENCE and LICEN[CS]E.* files in the 7 | package for specific licensing terms. 8 | -------------------------------------------------------------------------------- /licenses/no-source-code: -------------------------------------------------------------------------------- 1 | Gentoo license note: This package is distributed in binary form and 2 | its source code is not made available. This renders the package 3 | non-free in terms of the Free Software Definition [1], the Open Source 4 | Definition [2], or (for works other than software) the Definition of 5 | Free Cultural Works [3], even if it is distributed under a free 6 | software license. Source code is the preferred form in which a 7 | programmer would modify the work. 8 | 9 | Note to developers: The "no-source-code" license label must never be 10 | used on its own, but only along with the license under which the 11 | package is distributed. It should only be used together with licenses 12 | that would qualify as free when used for source code. 13 | 14 | [1] http://www.gnu.org/philosophy/free-sw.html 15 | [2] http://opensource.org/osd 16 | [3] http://freedomdefined.org/ 17 | -------------------------------------------------------------------------------- /licenses/raspberrypi-videocore-bin: -------------------------------------------------------------------------------- 1 | Note: this licence applies to the binaries in the bin, sbin, and lib 2 | sub-directories. The header files in the include sub-directory and the example 3 | code in src describes their licence at the top of the file. 4 | 5 | ---- 6 | 7 | Copyright (c) 2006, Broadcom Corporation. 8 | All rights reserved. 9 | 10 | Redistribution. Redistribution and use in binary form, without 11 | modification, are permitted provided that the following conditions are 12 | met: 13 | 14 | * This software may only be used for the purposes of developing for, 15 | running or using a Raspberry Pi device. 16 | * Redistributions must reproduce the above copyright notice and the 17 | following disclaimer in the documentation and/or other materials 18 | provided with the distribution. 19 | * Neither the name of Broadcom Corporation nor the names of its suppliers 20 | may be used to endorse or promote products derived from this software 21 | without specific prior written permission. 22 | 23 | DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 24 | CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, 25 | BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND 26 | FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 27 | COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 28 | INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 29 | BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS 30 | OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND 31 | ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR 32 | TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE 33 | USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH 34 | DAMAGE. 35 | 36 | -------------------------------------------------------------------------------- /reference/compile_run_benchmarks.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # 3 | # Compile and run various benchmarks for RPi3, in either 32-bit or 64-bit mode 4 | # 5 | # Download http://www.roylongbottom.org.uk/Raspberry_Pi_Benchmarks.zip 6 | # unzip, and enter the "Source Code" directory 7 | # 8 | # Can be run as regular, non-root user 9 | # You should probably run this on a text console, and ensure that 10 | # there is no desktop running ("sudo service xdm stop" on Gentoo; Raspbian 11 | # users may find it easiest to use: 12 | # "sudo systemctl set-default multi-user.target; sudo reboot"), and that you 13 | # have the CPU frequency scaling governor set to "performance" 14 | # (sudo echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor) 15 | # 16 | # When done, restore the default governor and desktop 17 | # ("sudo /etc/local.d/ondemand_freq_scaling.start; sudo service xdm start" 18 | # on Gentoo; Raspbian users may find it easiest to use: 19 | # "sudo systemctl set-default graphical.target; sudo reboot") 20 | # 21 | # Benchmark results are saved to to text files (DhryA8.txt etc.) 22 | # 23 | # Copyright (c) 2017 sakaki 24 | # License: GPL 3.0+ 25 | # NO WARRANTY 26 | 27 | set -e 28 | set -u 29 | 30 | if grep -q "aarch64" <(uname -a); then 31 | echo "Will build tests for 64-bit ARMv8" 32 | # as used on image 33 | CFLAGS="-lm -lrt -march=armv8-a+crc -mtune=cortex-a53 -O3 -pipe" 34 | V="8" 35 | else 36 | echo "Compiling tests for 32-bit ARMv7a" 37 | # per https://wiki.gentoo.org/wiki/Raspberry_Pi#Stage_3 38 | CFLAGS="-lm -lrt -march=armv7-a -mfpu=neon-vfpv4 -mfloat-abi=hard" 39 | CFLAGS="${CFLAGS} -O3 -pipe" 40 | V="7" 41 | fi 42 | 43 | echo "Deleting old binaries and result files..." 44 | # A7 = 32-bit A8 = 64-bit 45 | # FS = unsafe math optimizations (NEON) used 46 | # SP = single precision 47 | rm -f Dhry.txt whets.txt Linpack.txt LLloops.txt memSpeed.txt busSpeed.txt 48 | rm -f DhryA${V}.txt whetsA${V}.txt \ 49 | LinpackA${V}.txt LinpackA${V}SP.txt LinpackA${V}FSSP.txt \ 50 | LLloopsA${V}.txt memSpeedA${V}.txt memSpeedA${V}FS.txt \ 51 | busSpeedA${V}.txt 52 | rm -f dhrystonePiA${V} whetstonePiA${V} \ 53 | linpackPiA${V} linpackPiA${V}SP linpackPiA${V}FSSP \ 54 | liverloopsPiA${V} memspeedPiA${V} memspeedPiA${V}FS \ 55 | busspeedPiA${V} 56 | 57 | echo "Compiling tests..." 58 | gcc ${CFLAGS} -o whetstonePiA${V} whets.c cpuidc.c 59 | gcc ${CFLAGS} -o dhrystonePiA${V} dhry_1.c dhry_2.c cpuidc.c 60 | gcc ${CFLAGS} -o linpackPiA${V} linpack.c cpuidc.c 61 | gcc ${CFLAGS} -o linpackPiA${V}SP linpacksp.c cpuidc.c 62 | gcc ${CFLAGS} -funsafe-math-optimizations \ 63 | -o linpackPiA${V}FSSP linpacksp.c cpuidc.c 64 | gcc ${CFLAGS} -o liverloopsPiA${V} lloops2.c cpuidc.c 65 | gcc ${CFLAGS} -o memspeedPiA${V} memspeed.c cpuidc.c 66 | gcc ${CFLAGS} -funsafe-math-optimizations \ 67 | -o memspeedPiA${V}FS memspeed.c cpuidc.c 68 | gcc ${CFLAGS} -o busspeedPiA${V} busspeed.c cpuidc.c 69 | 70 | 71 | echo "Compiled - running tests - press at end of each" 72 | echo "to move to next" 73 | ./whetstonePiA${V} 74 | mv -v whets.txt whetsA${V}.txt 75 | ./dhrystonePiA${V} 76 | mv -v Dhry.txt DhryA${V}.txt 77 | ./linpackPiA${V} 78 | mv -v Linpack.txt LinpackA${V}.txt 79 | ./linpackPiA${V}SP 80 | mv -v Linpack.txt LinpackA${V}SP.txt 81 | ./linpackPiA${V}FSSP 82 | mv -v Linpack.txt LinpackA${V}FSSP.txt 83 | ./liverloopsPiA${V} 84 | mv -v LLloops.txt LLloopsA${V}.txt 85 | ./memspeedPiA${V} || true 86 | mv -v memSpeed.txt memSpeedA${V}.txt 87 | ./memspeedPiA${V}FS || true 88 | mv -v memSpeed.txt memSpeedA${V}FS.txt 89 | ./busspeedPiA${V} || true # these tests end with return(1) for some reason 90 | mv -v busSpeed.txt busSpeedA${V}.txt 91 | 92 | echo "" 93 | echo "CPU governor was" \ 94 | $(cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor) 95 | echo "(should be 'performance')" 96 | echo "" 97 | echo "All done!" 98 | -------------------------------------------------------------------------------- /reference/genup.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/GenPi64/gentoo-on-rpi-64bit/ab3a07e5115c428e9e6e7e023acd2bad0aa65421/reference/genup.pdf -------------------------------------------------------------------------------- /reference/migratation-from-sakaki-image.md: -------------------------------------------------------------------------------- 1 | # Migratation from Sakaki's image 2 | 3 | This assumes that you're using the latest available Sakaki's image. 4 | 5 | ## Binhost 6 | 7 | Please make sure that your /etc/portage/make.conf does not have a binhost set at all. 8 | 9 | Create a new file /etc/portage/binrepos.conf: 10 | ``` 11 | [genpi64-main-binhost] 12 | priority = 99 13 | sync-uri = https://packages.genpi64.com/ 14 | 15 | [genpi64-europe-binhost] 16 | priority = 98 17 | sync-uri = https://fi.packages.genpi64.com/ 18 | ``` 19 | 20 | ## Overlays 21 | 22 | You need to start by updating the genpi-overlay and sakaki-tools overlay locations to the correct ones. 23 | 24 | File /etc/portage/repos.conf/genpi64.conf: 25 | ``` 26 | [genpi64] 27 | 28 | location = /var/db/repos/genpi64 29 | sync-type = git 30 | sync-uri = https://github.com/GenPi64/genpi64-overlay.git 31 | priority = 100 32 | auto-sync = yes 33 | ``` 34 | 35 | File /etc/portage/repos.conf/sakaki-tools.conf: 36 | ``` 37 | [genpi-tools] 38 | 39 | location = /var/db/repos/sakaki-tools 40 | sync-type = git 41 | sync-uri = https://github.com/GenPi64/genpi-tools.git 42 | priority = 50 43 | auto-sync = yes 44 | ``` 45 | 46 | You will also need to use the main gentoo tree. 47 | 48 | File /etc/portage/repos.conf/gentoo.conf: 49 | ``` 50 | [DEFAULT] 51 | main-repo = gentoo 52 | 53 | [gentoo] 54 | location = /var/db/repos/gentoo 55 | sync-type = rsync 56 | sync-uri = rsync://rsync.gentoo.org/gentoo-portage 57 | auto-sync = yes 58 | ``` 59 | 60 | Please run `rm -r /var/db/repos/*` and then `emerge --sync` before continuing when you have edited those files. 61 | 62 | ## Profiles and meta package 63 | 64 | Select the new profile: `eselect profile set genpi64:default/linux/arm64/17.0/genpi64` or `eselect profile set genpi64:default/linux/arm64/17.0/genpi64/desktop`. 65 | Unmerge the obsolate meta packages: `emerge --unmerge dev-embedded/rpi-64bit-meta dev-embedded/rpi3-64bit-meta`. 66 | 67 | 68 | 69 | After doing all of that, update the system fully: `emerge -avg --update --newuse --deep @world`. 70 | 71 | -------------------------------------------------------------------------------- /reference/porthash.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/GenPi64/gentoo-on-rpi-64bit/ab3a07e5115c428e9e6e7e023acd2bad0aa65421/reference/porthash.pdf -------------------------------------------------------------------------------- /reference/showem.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/GenPi64/gentoo-on-rpi-64bit/ab3a07e5115c428e9e6e7e023acd2bad0aa65421/reference/showem.pdf --------------------------------------------------------------------------------