On Fri, Apr 26, 2024 at 10:19 PM Joe Nosay <[email protected]> wrote:
> Ok, > I will try to get back to this project after a few things in life. > I did run the autocfg or so script on an aarch64 device running android. > For reason that the ppc/ppc64 mac devices have a flattened device > tree/device tree and not the direct acpi and boot loader: > 1. The device needs to be checked from the open firmware boot loader that > free bsd must chain load into before loading freebsd. > 2. UEFI and EFI do not provide the exact same function as the open > firmware loader, das uboot, the android RISC loader, > petitboot, or the sparc/64 boot loader. > 3. I have not checked if there are any "--help" options for autocfg while > there are for "configure --help". > 4. I need to buy more RAM since 13.x allows over the 2gb hardware limit. > I have two imac g5 devices with the second being an isight. That one will > be dedicated to freebsd. > 5. I am wondering if the kernel change on 13.x for memory can be written > to the netbsd kernel to allow a greater gb ram access. > If not, I may be trying and comparing brl.tty build between Free and Net > BSDs on similar machines. The other is a standard imac g5 non isight. > 6. If anyone does this along with me when I have a good start: > a. You will have to build the system from ports and list your options. > b. This project will be shared with the American with disabilities act. > This will allow people to know the exact setup. I have thought about it. > PKg build up does not give the reason for each option when making the > package. > For example, if heimdall options causes more trouble and that is the > package option > then using the package will cause trouble in testing the brl.tty > application/service. > > RISC and CISC are not the same. > Compiling, functioning, etc > even the crystal oscillator are completely different. > I do not currently know which RISC powerpc/power devices run as bare metal > or through some > virtual setup. > I need to make sure that g5/970 ?? run as bare metaal and that bare metal > can be accesed on others. > LIve CD/DVD/usb images will need to be tested and ran. > I do not know as to the best dm/gui environment and the amount of > available space. > Is it possible to have a live or "permanent" system that is able to load > and test the proper drivers randomly. > I do npot have any type of account with the open power foundation. IBM > will definitely need to be contacted > for some information. > > > > On Sat, Apr 6, 2024 at 10:01 PM Brian Buhrow <[email protected]> wrote: > >> hello. I built Brltty a number of years ago on NetBSD, which is >> a close sibling of >> FreeBSD. So, I think you'll find it pretty easy to accomplish the task. >> -thanks >> -Brian >> >> On Apr 7, 3:25am, Alfonso Sabato Siciliano wrote: >> } Subject: Re: [BRLTTY] brltty.app on FreeBSD >> } --===============5576965544286566759== >> } Content-Type: multipart/alternative; >> boundary="0000000000004e34d00615779165" >> } >> } --0000000000004e34d00615779165 >> } Content-Type: text/plain; charset="UTF-8" >> } > Has anyone built brltty on a ppc64 machine and or FreeBSD? >> } > >> } >> } I am interested to build brltty on FreeBSD. Currently I am trying to >> build, >> } run and use brltty with the xwindow emulator on Linux, then I=E2=80=99 >> ll s= >> } tart to >> } try to build and/or adapt brltty on FreeBSD. >> } >> } Best regards, >> } Alfonso >> _______________________________________________ >> This message was sent via the BRLTTY mailing list. >> To post a message, send an e-mail to: [email protected] >> For general information, go to: http://brltty.app/mailman/listinfo/brltty >> >
_______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
