Is someone working on HFS+ support ?

Is someone working on HFS+ support ?

[Benjamin Herrenschmidt]

The question is in the title... 


-- 
           Perso. e-mail: <mailto:bh40@calva.net>
           Work   e-mail: <mailto:benh@mipsys.com>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: Is someone working on HFS+ support ?

[phandel]

On Wed, 18 Aug 1999, Benjamin Herrenschmidt wrote:

> The question is in the title... 

I sent a note to asun@u.washington.edu, who said he was going to clean up
what he had before he would release his work so far.  Last I heard, he was
in the thick of work, but was planning on releasing something soon.


Thanks,
Pete

-- 
Peter F. Handel          "[The anti-Christ] also forced everyone, small and
phandel@cise.ufl.edu      great ... to receive a mark [smart card?] on his
www.cise.ufl.edu/~phandel right hand or on his forehead, so that no one could
FAX: (561) 619-8051       buy or sell unless he had the mark"-Revelation13:16


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

BootX enhancement request

[brad allison]

I'm not sure how hard/not hard this would be to do, but right now in order
to change resolutions I have to boot into MacOS, set my resolution, launch
BootX, boot into init 3, run Xautoconfig, boot into init 5.

That's a lot of work to just change the resolution for X.

It would be nice if you could set the resolution and color from BootX on
boot up.

If there's a easier way to change pixel depth and resolution from inside X
please let me know....

-b

--
AOL SAPI 		                        703.265.0908     AIM:jackal242
http://jackal.fudge.org        `I was never more certain of how far away I was
from my goal than when I was standing right beside it.' - Ethan Hawke, Gattaca


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[Mike Lambert]

brad allison wrote:
> 
> I'm not sure how hard/not hard this would be to do, but right now in order
> to change resolutions I have to boot into MacOS, set my resolution, launch
> BootX, boot into init 3, run Xautoconfig, boot into init 5.

One way would be to add a line to your rc.local file to check for and
run Xautoconfig automatically on startup.

> It would be nice if you could set the resolution and color from BootX on
> boot up.

This would require using  a video hw specific driver such as "atyfb" or "aty128fb".
 
-mike

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[Robert Shaw]

Brad,

Once again, you DO NOT NEED TO DO THIS! The B&W G3 now has video support.

If you've downloaded the latest kernel from my web-site, you can specify the
video mode you want from the kernel arguments of BootX. Add the following to you
kernel arguments:

video=aty128fb:vmode:17,cmode:32

That will give you 1024x768 @ 75Hz, w/32bpp. Piece of cake, no init'ing, no
rebooting, no running Xautoconfig.

The FAQ page at my site (http://www.inficad.com/~rshaw/g3_faq.shtml) also has the
reproduction of the vmode settings that are available. They work, and no running
of Xautoconfig is needed.

-Robert
rshaw@inficad.com
http://www.inficad.com/~rshaw/


brad allison wrote:

> I'm not sure how hard/not hard this would be to do, but right now in order
> to change resolutions I have to boot into MacOS, set my resolution, launch
> BootX, boot into init 3, run Xautoconfig, boot into init 5.
>
> That's a lot of work to just change the resolution for X.
>
> It would be nice if you could set the resolution and color from BootX on
> boot up.
>
> If there's a easier way to change pixel depth and resolution from inside X
> please let me know....
>
> -b
>
> --
> AOL SAPI                                        703.265.0908     AIM:jackal242
> http://jackal.fudge.org        `I was never more certain of how far away I was
> from my goal than when I was standing right beside it.' - Ethan Hawke, Gattaca


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

video driver ( was Re: BootX enhancement request )

[john s anderson]

Along the lines of this thread, does anyone know the supplied video
drivers work with the internal video of a 7500? Or should I just stick to
the 'No Video Driver' option?

In past experiments, unselecting No Video Driver lead to the 'grey square
behind the pointer' problem with this box.

Thanks for any help,
john.

-- 
----------------------------------------------------------------
John S Jacobs Anderson                      jacobs@azstarnet.com
www.treefort.org/~jacobs/ <--   GeneHack (bioinfo*linux*opinion)


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[brad allison]

On Mon, 23 Aug 1999, Robert Shaw wrote:

> Brad,
> 
> Once again, you DO NOT NEED TO DO THIS! The B&W G3 now has video support.
> 
> If you've downloaded the latest kernel from my web-site, you can specify the
> video mode you want from the kernel arguments of BootX. Add the following to you
> kernel arguments:
> 
> video=aty128fb:vmode:17,cmode:32
> 
> That will give you 1024x768 @ 75Hz, w/32bpp. Piece of cake, no init'ing, no
> rebooting, no running Xautoconfig.
> 

I think you missed my point.  Don't get me wrong, that's cool to know.
But I was thinking more along the lines of a drop down menu to set the
resolution from BootX rather than cryptic kernel arguements.

It seems the 2.2.10 kernel will not sync to the video settings at all
without the kernel arguements.

> The FAQ page at my site (http://www.inficad.com/~rshaw/g3_faq.shtml) 
> also has the
> reproduction of the vmode settings that are available. They work, and
> no running of Xautoconfig is needed.

Well i think putting Xautoconfig in the rc.local file is still a good
idea.

-b


> 
> 
> brad allison wrote:
> 
> > I'm not sure how hard/not hard this would be to do, but right now in order
> > to change resolutions I have to boot into MacOS, set my resolution, launch
> > BootX, boot into init 3, run Xautoconfig, boot into init 5.
> >
> > That's a lot of work to just change the resolution for X.
> >
> > It would be nice if you could set the resolution and color from BootX on
> > boot up.
> >
> > If there's a easier way to change pixel depth and resolution from inside X
> > please let me know....
> >
> > -b
> >
> > --
> > AOL SAPI                                        703.265.0908     AIM:jackal242
> > http://jackal.fudge.org        `I was never more certain of how far away I was
> > from my goal than when I was standing right beside it.' - Ethan Hawke, Gattaca
> 

--
AOL SAPI 		                        703.265.0908     AIM:jackal242
http://jackal.fudge.org        `I was never more certain of how far away I was
from my goal than when I was standing right beside it.' - Ethan Hawke, Gattaca


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[Tom Rini]

On Mon, 23 Aug 1999, brad allison wrote:

> On Mon, 23 Aug 1999, Robert Shaw wrote:
> 
> > Brad,
> > 
> > Once again, you DO NOT NEED TO DO THIS! The B&W G3 now has video support.

This, BETA, driver. :)

> I think you missed my point.  Don't get me wrong, that's cool to know.
> But I was thinking more along the lines of a drop down menu to set the
> resolution from BootX rather than cryptic kernel arguements.

So you want BootX to be able to do what Monitors & Sound can do.  Either
pick a mode there and use BootX from MacOS, or once 2.4.0 rolls around,
specify video=aty128fb:1024x768@75 (or so).  There is no need for BootX to
do this.

> It seems the 2.2.10 kernel will not sync to the video settings at all
> without the kernel arguements.

What, aty128fb?  It's beta and not done.  You're prolly better off using
No Video Driver, unles you're gonna play w/ the source (Anthony, speak up
if i'm wrong). :)

> > The FAQ page at my site (http://www.inficad.com/~rshaw/g3_faq.shtml) 
> > also has the
> > reproduction of the vmode settings that are available. They work, and
> > no running of Xautoconfig is needed.
> 
> Well i think putting Xautoconfig in the rc.local file is still a good
> idea.

Xautoconfig is nice for monitors that don't work right w/ Xconfigurator.
It's not a tool for "No Video Driver" machines, it's a tool for wierd
monitors/easier to setup X.

---
Tom Rini (TR1265)
http://gate.crashing.org/~trini/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[Robert Shaw]

> I think you missed my point.  Don't get me wrong, that's cool to know.
> But I was thinking more along the lines of a drop down menu to set the
> resolution from BootX rather than cryptic kernel arguements.

Ok, that's reasonable. Any thoughts Ben?

> It seems the 2.2.10 kernel will not sync to the video settings at all
> without the kernel arguements.

Strange, mine does. :|
Have you tried the latest 2.2.10 kernel I posted last night? Does it mess up also?

>
> Well i think putting Xautoconfig in the rc.local file is still a good
> idea.
>

Not if you make changes to the XF86Config file for the USB xkb stuff. Xautoconfig
will mess it all up and switch it back to PC settings. There is a warning in the
Kernel HOWTO about this when setting up the xkb settings.

-Robert
mailto:rshaw@inficad.com
http://www.inficad.com/~rshaw/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[Robert Shaw]

> This, BETA, driver. :)

Yeah, but it works, and it's much faster than the plain frame buffer device. :)

> What, aty128fb?  It's beta and not done.  You're prolly better off using
> No Video Driver, unles you're gonna play w/ the source (Anthony, speak up
> if i'm wrong). :)

It may be beta, but it works just fine. I've had several users indicate it works
without any problems.

--
-Robert
mailto:rshaw@inficad.com
http://www.inficad.com/~rshaw/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[Jerry Quinn]

>> "Tom" == Tom Rini <trini@disparity.net> writes:

 Tom> So you want BootX to be able to do what Monitors & Sound can do.  Either
 Tom> pick a mode there and use BootX from MacOS, or once 2.4.0 rolls around,
 Tom> specify video=aty128fb:1024x768@75 (or so).  There is no need for BootX
 Tom> to do this.

Probably more to the point, we should strive to provide some easy way of doing
it.  How do MacOS and Windows deal with the problem of different monitors and
resolutions?  I know on the Mac so far, I automatically get the available
resolutions, although Apple-style monitors have extra sense pins to provide
the info.

Ideally, I shouldn't have to ever think about my monitor or have to add
command line args to the kernel.  Such twiddling should be as rare as
possible. 

-- 
Jerry Quinn                             Tel: (514) 761-8737
jquinn@nortelnetworks.com               Fax: (514) 761-8505
Speech Recognition Research


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[David A. Gatwood]

On Mon, 23 Aug 1999, Jerry Quinn wrote:

> Probably more to the point, we should strive to provide some easy way of doing
> it.  How do MacOS and Windows deal with the problem of different monitors and
> resolutions?  I know on the Mac so far, I automatically get the available
> resolutions, although Apple-style monitors have extra sense pins to provide
> the info.
> 
> Ideally, I shouldn't have to ever think about my monitor or have to add
> command line args to the kernel.  Such twiddling should be as rare as
> possible. 

Feel free to look at the code MkLinux hass to read the sense pins.... 
Granted, it's not actually being _used_ for anything, since MkLinux
doesn't change resolution, but it's there in the original PDM video
driver.  There will obviously be differences for other video hardware, but
it _might_ at least provide some useful inspiration or something.


David


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

imac exception (Re: BootX enhancement request)

[Brad Midgley]

it should be noted that the imac, although it has the same 15-pin video
connector internally, doesn't follow the rules and apply the right signals
to its sense pins. so you need a special case in your detection code for
this beast. (the signals from the sense pins suggest the computer use a
resolution/synch that the monitor doesn't even support)

> Feel free to look at the code MkLinux hass to read the sense pins.... 
> Granted, it's not actually being _used_ for anything, since MkLinux
> doesn't change resolution, but it's there in the original PDM video
> driver.  There will obviously be differences for other video hardware, but
> it _might_ at least provide some useful inspiration or something.

Brad
brad@pht.com | http://www.pht.com/~brad/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[brad allison]

On Mon, 23 Aug 1999, Robert Shaw wrote:

> > This, BETA, driver. :)
> 
> 
> It may be beta, but it works just fine. I've had several users indicate it works
> without any problems.
> 

I'm using it. 

Works great.  I've got a G3 450mhz (rev2) and a SGI 21" monitor.  

I tested the precompiled 2.2.6 and the 2.2.10 off Shaw's site.

The 2.2.6 kernel worked without having to do anything special.  The 2.2.10
kernel needed the kernel arguements to synch to my monitor.

-b


--
AOL SAPI 		                        703.265.0908     AIM:jackal242
http://jackal.fudge.org        `I was never more certain of how far away I was
from my goal than when I was standing right beside it.' - Ethan Hawke, Gattaca


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[Peter Chang]

Note: I'm not really active on the linuxppc-dev list (read: lurker), 
but I assume that all of the people on the 'to' list are on the list 
so I've trimmed it back to just the list.

> >> "Tom" == Tom Rini <trini@disparity.net> writes:
>
> Tom> So you want BootX to be able to do what Monitors & Sound can do.  Either
> Tom> pick a mode there and use BootX from MacOS, or once 2.4.0 rolls around,
> Tom> specify video=aty128fb:1024x768@75 (or so).  There is no need for BootX
> Tom> to do this.

I agree w/ this, if mostly because bootX would either need to do a 
lot of querying to determine what the board/monitor combo could do or 
there would be yet another list of supportable modes that might get 
out of sync w/ what's already in the X config stuff.

At 16:56 -0400 08.23.1999, Jerry Quinn wrote:
>How do MacOS and Windows deal with the problem of different monitors and
>resolutions?  I know on the Mac so far, I automatically get the available
>resolutions, although Apple-style monitors have extra sense pins to provide
>the info.

W/ the coming of win9x, the pnp stuff wants to load 'extra' 
information about monitors etc taht it detects. This information 
'overrides' any monitor sense stuff that might be present (I've never 
seen a pc monitor like this), and restricts the list of availible 
modes presented to the user. I've since lost the brain cells involved 
(thank goodness), but you can 'hand edit' the .inf file (or whatever) 
to get modes that you know the monitor supports but that are not 
advertised. (Well, my co-workers at 3dfx and I would do this because 
we 'knew' our brand new viewsonic monitors could do a lot more than 
whatever appeared in the list).

I think that the lack of sense pins for normal vga connectors is part 
of the reason why windows still asks if the test pattern appears 
correctly on the monitor. It knows what the card can support, but not 
whether the user is using some crappy monitor that can't synch.

\p

---
We all enter this world in the same way:
naked; screaming; soaked in blood.
But if you live your life right, that kind of
thing doesn't have to stop there. -- Dana Gould

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[anthony tong]

Tom Rini (Mon, Aug 23, 1999 at 04:27:46PM -0400):
> > I think you missed my point.  Don't get me wrong, that's cool to know.
> > But I was thinking more along the lines of a drop down menu to set the
> > resolution from BootX rather than cryptic kernel arguements.
> 
> So you want BootX to be able to do what Monitors & Sound can do.  Either
> pick a mode there and use BootX from MacOS, or once 2.4.0 rolls around,
> specify video=aty128fb:1024x768@75 (or so).  There is no need for BootX to
> do this.

If you have a version of MacOS that saves the monitor mode in nvram,
you shouldn't need to give any kernel arguments. Alternatively you
can use the linuxpmac tool nvvideo to set this.

It should be simple to add modedb support for the time being as well.

> > It seems the 2.2.10 kernel will not sync to the video settings at all
> > without the kernel arguements.

The default (without kernel arguments) is 640x480-60, unless you have
a video mode already set in nvram.

> What, aty128fb?  It's beta and not done.  You're prolly better off using
> No Video Driver, unles you're gonna play w/ the source (Anthony, speak up
> if i'm wrong). :)

If it works, use it, if not, send me an email. :)


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[Paul Mackerras]

anthony tong <atong@uiuc.edu> wrote:

> If you have a version of MacOS that saves the monitor mode in nvram,
> you shouldn't need to give any kernel arguments. Alternatively you
> can use the linuxpmac tool nvvideo to set this.

Yep.  There are two problems at the moment, which I should get off my
butt and fix. :-)

The first is that the current machines use a different structure for
nvram, based on the CHRP spec, which means that just using a fixed
offset in nvram doesn't work.  In fact it seems like macos adds a OF
property with a really strange encoding to store arbitrary bits of
information for the device drivers for arbitrary devices.

The second is that macos is now using mode numbers > 20.  I haven't
worked out the correspondence yet.

Paul.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: BootX enhancement request

[Tom Rini]

On Mon, 23 Aug 1999, Jerry Quinn wrote:

> >> "Tom" == Tom Rini <trini@disparity.net> writes:
> 
>  Tom> So you want BootX to be able to do what Monitors & Sound can do.  Either
>  Tom> pick a mode there and use BootX from MacOS, or once 2.4.0 rolls around,
>  Tom> specify video=aty128fb:1024x768@75 (or so).  There is no need for BootX
>  Tom> to do this.
> 
> Probably more to the point, we should strive to provide some easy way of doing
> it.  How do MacOS and Windows deal with the problem of different monitors and
> resolutions?  I know on the Mac so far, I automatically get the available
> resolutions, although Apple-style monitors have extra sense pins to provide
> the info.

Don't they both stick you at 640x480@60, and make you choose up from
there?  (I know I've seen waaay to many  640x480 PCs around in these dorms
lately).  There are ways to sense modes, and it is implemented in some
drivers (most, iirc)

> Ideally, I shouldn't have to ever think about my monitor or have to add
> command line args to the kernel.  Such twiddling should be as rare as
> possible. 

So set something in MacOS. :)

---
Tom Rini (TR1265)
http://gate.crashing.org/~trini/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]