From nobody Tue Mar 19 07:25:23 2024 X-Original-To: ppc@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TzNY51xnWz5DkqW for ; Tue, 19 Mar 2024 07:25:29 +0000 (UTC) (envelope-from stefane@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TzNY41LHyz4Hwc for ; Tue, 19 Mar 2024 07:25:28 +0000 (UTC) (envelope-from stefane@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=fltUdYL1; dmarc=pass (policy=none) header.from=riseup.net; spf=pass (mx1.freebsd.org: domain of stefane@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=stefane@riseup.net Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4TzNY23MKYz9sVX for ; Tue, 19 Mar 2024 07:25:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1710833126; bh=Pu7WuI+C1plB1aYxvXjl40XrH5CN4suWH2XPsHzS0vY=; h=Date:Subject:To:References:From:In-Reply-To:From; b=fltUdYL1c2GC1AFG8YTQdPy60td98x1gpsSckl2FJUhfKmCGhhLlLAKAZcD6IHfyb Q12Z4BHLvgq37YrV7TTBsTNK3Z48Pg7WodzP/Nvurqjv4jW3wOPTdNnP5ms2E+jgQ+ KkNcg8MmPp9k4D4UYjS/3LZ9wAkpAMZJ9UESJ9Gc= X-Riseup-User-ID: B117A03C8DB3E4970970DCED6FA1316CB4D70FEDE6094BBD2818A752A2BCC811 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4TzNY14ycCzJsrw for ; Tue, 19 Mar 2024 07:25:25 +0000 (UTC) Content-Type: multipart/alternative; boundary="------------nvVzlKobh1DN2r0xqwqfkk0U" Message-ID: <8297c3c2-5807-46c8-85dc-135c8c228455@riseup.net> Date: Tue, 19 Mar 2024 08:25:23 +0100 List-Id: Porting FreeBSD to the PowerPC List-Archive: https://lists.freebsd.org/archives/freebsd-ppc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org MIME-Version: 1.0 Subject: Re: On the project. Content-Language: fr, fr-FR, en-US To: ppc@freebsd.org References: From: =?UTF-8?Q?St=C3=A9fane?= In-Reply-To: X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.27 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_MIXED_CHARSET(0.83)[subject]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[ppc@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[ppc@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~] X-Rspamd-Queue-Id: 4TzNY41LHyz4Hwc This is a multi-part message in MIME format. --------------nvVzlKobh1DN2r0xqwqfkk0U Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hello I'm not a top person concerning FreeBSD on PPC. However, I've tried successfully installing FeeBSD on an old PPC Mac except the XWindow interface. If someone knows the way to install the XWindow on the FreeBSD, I'll be deeply grateful. Stéfane http://sparis.free.fr/ Le 18/03/2024 à 19:30, Joe Nosay a écrit : > Researching, I have come upon information that the iSight will hold a > maximum of 4.5 GB RAM while the other iMac G5 > is limited at 2GB RAM. > Brltty needs to have ./autogen ran first. > cat configure|more > I do not understand the mindset of this community at times. > I am very certain that the Americans with Disabilities Act and the > visually impaired community would gladly - and there is information on > the forums - work again - notice the word "again" because they have > asked multiple times in the past - with the FreeBSD community. > I am not blind; yet, it seems to make more sense in the FreeBSD > community to set up NetFlix while ignoring millions of people who > would benefit from FreeBSD working with braille devices. > Before any of you reply with sarcasm or excuses- > I need neurosurgery. > It is a shame that someone in bad health as myself is the only one > willing to work on this. > > > On Tue, Mar 5, 2024 at 9:28 AM Joe Nosay wrote: > > I have two iMac G5s: one single core with 2G RAM, the other dual > core with 512M RAM. > What is the maximum RAM that each will be able to use under FreeBSD? > The project will be brltty on PPC64 and others that use a bootloader. > PPC64 will be the initial setup. > I have read through the config/configure file of the brltty source > code. > The open firmware references in the FreeBSD PPC64 were also read. > Before I restart on the project, here is the basic information: > Brltty configure will need to be rewritten to include the open > firmware references. > I have never used the FreeBSD version of the device tree > referenced to > as the "flattened device tree." The only use/ reference/ > experience was > directly accessing open firmware from the forth prompt. > Currently, I have no braille devices here due to an extremely limited > income. I'm going to do a port build and not a package setup of both > computers. More RAM will need to be purchased Because the > computers are at someone else's place and that I need to purchase > my own mobile dedicated network along with wireless dongles, this may > take some time. > I will inform you (pl) again when the next step or so is done. > --------------nvVzlKobh1DN2r0xqwqfkk0U Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hello

I'm not a top person concerning FreeBSD on PPC.
However, I've tried successfully installing FeeBSD on an old PPC Mac except the XWindow interface.
If someone knows the way to install the XWindow on the FreeBSD, I'll be deeply grateful.

Stéfane http://sparis.free.fr/

Le 18/03/2024 à 19:30, Joe Nosay a écrit :
Researching, I have come upon information that the iSight will hold a maximum of 4.5 GB RAM while the other iMac G5
is limited at 2GB RAM.
Brltty needs to have ./autogen ran first.
cat configure|more
I do not understand the mindset of this community at times.
I am very certain that the Americans with Disabilities Act and the visually impaired community would gladly - and there is information on
the forums - work again - notice the word "again" because they have asked multiple times in the past - with the FreeBSD community.
I am not blind; yet, it seems to make more sense in the FreeBSD community to set up NetFlix while ignoring millions of people who would benefit from FreeBSD working with braille devices.
Before any of you reply with sarcasm or excuses-
I need neurosurgery.
It is a shame that someone in bad health as myself is the only one willing to work on this.


On Tue, Mar 5, 2024 at 9:28 AM Joe Nosay <superbisquit@gmail.com> wrote:
I have two iMac G5s: one single core with 2G RAM, the other dual core with 512M RAM.
What is the maximum RAM that each will be able to use under FreeBSD?
The project will be brltty on PPC64 and others that use a bootloader.
PPC64 will be the initial setup.
I have read through the config/configure file of the brltty source code.
The open firmware references in the FreeBSD PPC64 were also read.
Before I restart on the project, here is the basic information:
Brltty configure will need to be rewritten to include the open firmware references.
I have never used the FreeBSD version of the device tree referenced to 
as the "flattened device tree." The only use/ reference/ experience was
directly accessing open firmware from the forth prompt.
Currently, I have no braille devices here due to an extremely limited
income. I'm going to do a port build and not a package setup of both
computers. More RAM will need to be purchased Because the 
computers are at someone else's place and that I need to purchase 
my own mobile dedicated network along with wireless dongles, this may
take some time. 
I will inform you (pl) again when the next step or so is done.

--------------nvVzlKobh1DN2r0xqwqfkk0U--