| |
| |
| |
|
Page: 1 2 3 4 5 6 7
Comments:
<0> so I figured out how to set a property in pic16lc, but how to I get that property over in xboxfb?
<1> hey
<1> You said xboxfb works with component cables if you use a 720x480 framebuffer, correct?
<0> right
<1> ok
<0> it is a bit off the screen though.
<1> How so?
<0> overscanned on my hdtv
<1> oh, that's normal
<0> right, just pointing it out. :)
<1> and we can use rasops to put a border around the text
<0> from looking at all the proplib stuff, I can't figure out how to p*** a property between two devices.
<1> I'm working on it, no worries :)
<0> ok
<1> I moved the nforce ethernet hack from i386/machdep.c to xbox/xbox.c
<1> and call xbox_startup() from cpu_startup()
<1> within xbox_startup(), I create a prop_dictionary_t named 'xbox_properties'
<1> there is a function exported named xbox_get_prop_dictionary() that returns xbox_properties
<1> so if avpack is component you want to run at 720x480?
<1> what about vga?
<0> 720x480 is right for component, not sure on the others.
<0> I can check what cromwell does, since that is what we need to setup for anyway
<1> k
<1> /* check which AV pack is connected */
<1> pic16lc_read_1(sc, PIC16LC_REG_AVPACK, &avpack);
<1> xbox_properties = xbox_get_prop_dictionary();
<1> if (xbox_properties) {
<1> prop_number_t pn;
<1> pn = prop_number_create_integer(avpack);
<1> K***ERT(pn != NULL);
<1> (void)prop_dictionary_set(xbox_properties, "xbox-avpack", pn);
<1> prop_object_release(pn);
<1> }
<1> I have this in pic16lc_attach
<0> ok and just doing a prop_dictionary_get similarly in xboxfb?
<1> I believe so
<1> Let me try
<0> looks like VGA is setup for 800x600
<1> heh, neat
<1> can't we just figure out how to set it up and do it ourselves? or is it tricky?
<0> looks pretty complicated. basically driving the nvidia chip and the encoder.
<0> would need a full nvidiafb driver I guess.
<1> ah
<1> well, I would expect the encoder is already setup
<1> we can run the desktop resolution independent of the tv encoder resolution
<1> sorry, "console"
<1> I'm used to having this same discussion w/ coworkers when talking about WinCE ;)
<0> got it
<0> it looks like hdtv=720x480, vga=800x600 and others are 640x480 typically.
<0> possibly 640x576 for PAL or scart etc
<0> haven't seen that.
<1> So basically this is all xromwell's fault
<0> heh, yah, it is setting up the framebuffer for us.
<0> cromwell calls type 0x02 VGA_SOG and type 0x07 VGA
<0> but the PIC page calls 0x02 VGA and 0x07 none
<0> but it seems to set both VGA types to 800x600. :)
<1> stupid cromwell
<1> ok, testing w/ proplib changes
<1> comes up 640x480 with SD cables attached, let me find my HD cable
<1> uh oh, hard to boot without a display attached :p
<0> well I can test it.
<1> It's ok, right+a when the green led flashes ;)
<1> xboxfb0 at pci1 dev 0 function 0: 720x480, 32 bit framebuffer console
<1> cool, now to bring this thing to a room with an hdtv to try it for real
<0> yup
<0> prepare to be annoyed by overscan. :)
<1> hehe
<1> ****, wireless network in th eother room is on a different subnet
<0> well you don't need network to read the screen
<1> I need it to tftp boot a kernel..
<0> true
<1> no luck :(
<0> as in the display is bad or with network?
<1> display is bad
<0> cromwell is ok though?
<1> yep
<1> so, plan B
<0> and is cromwell HD or 4:3?
<1> forget dev properties, we'll just detect the damn thing in xboxfb_cnattach
<0> I guess 16:9 or 4:3?
<0> well you should try hard coding to 720 and make sure it works on your TV
<1> I tried on two different TVs
<0> my Xbox is setup for 16:9 widescreen by default
<0> so if you have it setup for 4:3 but on hdtv cables it might get hosed.
<0> though cromwell seems to explicitly set to 720x480 if HDTV cables.
<0> I can test it on my hdtv
<1> Believe me, it's not the TV..
<1> It was my broken logic in trying to change resolutions on the fly
<1> The problem with doing it the "clean" proplib way is that I will still get garbage text at the beginning
<1> I have a plan on how to make it auto-detect in xboxfb_cnattach so all will be nice :)
<2> aaigh
<2> can anyone who has an i386-current system tell me what size bootxx_cd9660 is supposed to be?
<1> mine is 2k
<2> thanks
<2> my build of -current is dying at create instkernel/netbsd-INSTALL_XEN3_DOMU.gz
<1> great, now xboxfb is all ****ed up :)
<0> oops, too much hacking.
<1> It's detecting an HDTV avpack when an SD one is attached
<2> anyone running a core 2 duo with amd64 system?
<3> heya
<2> nobody wants to help with my boring core 2 duo
<1> mspwned!
<2> they're all netbsd-ing the Xbox
<0> all I have is a core duo Mac. :)
<1> ****! what the hell is going wrong here
<0> well and a couple of Xboxes.
<1> avpack = xboxfb_get_avpack();
<1> switch (avpack) {
<1> case PIC16LC_REG_AVPACK_HDTV:
<1> ri->ri_width = SCREEN_WIDTH_HDTV;
<1> ri->ri_height = SCREEN_HEIGHT;
<1> break;
<2> I have a core duo mac, too. I want core 2 duo.
<1> default:
<1> ri->ri_width = SCREEN_WIDTH_SDTV;
<1> ri->ri_height = SCREEN_HEIGHT;
<1> break;
<1> }
<1> am I completely retarded and that looks wrong?
<3> Shaded- it looks okay to me
<2> looks ok to me
<2> not that I know what you're doing
<1> for some reason it's selecting the HDTV path when get_avpack "should" return something else
<4> htodd: I have a core2 system, lemme check
<5> hi andrew!
<1> hubert!
<0> hey
<4> oh, hm. Running Xen3, I forgot. :)
<1> I put a boot CD image, root fs tgz, and a quick HOWTO on nbftp
<0> did you printf avpack to make sure it is sane? :)
<4> (x86, not amd64)
<1> I'm printing it now
<5> jared!
<1> avpack is 0x01
<1> what in the name of **** is going on here
<5> jared: great news - tell the world! :-)
<1> oh, 0x01 is hdtv, wtf
<3> what's PIC16LC_REG_AVPACK_HDTV?
<2> heh
<0> yah
<0> sounds like the switch is working. :)
<1> but it's SUPPOSED to return 0x06
<3> so maybe you should check xboxfb_get_avpack()
<2> riz: are you just using the regular i386?
<0> maybe you're returning 0 or 1 instead of the register.
<4> yeah, i386 dom0
<1> I am, get_avpack does a bus_space_map, calls xboxfb_smbus_pic_read, then bus_space_unmap
<4> well, i686, anyway ;)
<1> if either bus_space_map or xboxfb_smbus_pic_read fail, it should return PIC16LC_REG_AVPACK_DISCONNECTED
<0> did you power cycle after swapping the cable? :)
Return to
#netbsd
or
Go to some related
logs:
gulfnewsuae
#politics
#gamedev
160grain 9mm
#heroin
#beginner
#beginner
#politics
#beginner
short bodybuilders
|
|