Jump to content

Chameleon v2.1 (Main Trunk)

ErmaC

By ErmaC,
in Chameleon

 Share
595 posts in this topic

Recommended Posts

Kabyl
Kabyl
Posted
Posted
Your source code (changes) should have been made available from day – along with the product when it was released – and unconditionally. All conform the license.

That should have been the case.

 

So how many lines were changes? I ask this because your made your post days ago already, and a simple look at the source code, with help of diff / FileMerge (et all) is just a manner of minutes. Not days. I'd say go with github because it is taking too long.

Maybe you're loosing track of time or something, but he posted that yesterday.

 

I got the patch yesterday night, and created the branch this morning.

 

This is also why I don't like the 'we' part in voodoo because I don't have a crystal ball. I am clearly not part of the voodoo magic inner circle, and thus I (and everybody else here) will have to wait for 'someone' to say magically yes (or no). That IMHO is wrong.

eeeerm.. what are you talking about? what's wrong with voodoo? or what is wrong that voodoo did?

Link to comment
Share on other sites
Time2Retire
Time2Retire
Posted
Posted
Maybe you're loosing track of time or something, but he posted that yesterday.

Or I see things a bit differently. I mean his initial post was made on April 27. That's almost six days ago. And that was why I said that things are taking too long. Not blaming you for being slow or lazy but everything is just going tediously slow IMHO.

 

I got the patch yesterday night, and created the branch this morning.

But without the patch applied. Correct?

 

eeeerm.. what are you talking about? what's wrong with voodoo? or what is wrong that voodoo did?

Wrong? Well. That might be too strong. However. Nobody will have to ask anyone over at Github for approval.

You just visit the place and get going. This way things could have gone faster. That is if they want it that way.

 

Also. I was quite surprised to read this comment:

"we would like to take a look at what you've done"

That seems to have delayed it even more. By at least a couple of days. Again. This is not your fault, but you do happen to sit on a patch that might be interesting for other people. We still don't have access to it. We still have to wait for a magical answer (action) from now voodoo member MacMan.

 

LOL I don't need to say that I'm impatient anymore, because that should have been pretty obvious by now already :)

 

Yeah yeah. I know. People are busy. Have other things to do. The more reason for a quick commit of your changes ;)

Link to comment
Share on other sites
Kabyl
Kabyl
Posted
Posted
Or I see things a bit differently. I mean his initial post was made on April 27. That's almost six days ago. And that was why I said that things are taking too long. Not blaming you for being slow or lazy but everything is just going tediously slow IMHO.

You said that I'm slow and lazy, then after the fact, you say you're not blaming me? that's weird.

 

But without the patch applied. Correct?

He asked for a branch, It's up to him to commit his patches.

 

Wrong? Well. That might be too strong. However. Nobody will have to ask anyone over at Github for approval.

You just visit the place and get going. This way things could have gone faster. That is if they want it that way.

The Voodoo forge was created to host Chameleon and a few other projects under the Voodoo name. It's not a project hosting site like github where anyone can create any project, you're comparing 2 different things.

 

Also. I was quite surprised to read this comment:
"we would like to take a look at what you've done"

Yes, because I'm not going to give write access to anyone asking for it.

 

That seems to have delayed it even more. By at least a couple of days. Again. This is not your fault, but you do happen to sit on a patch that might be interesting for other people. We still don't have access to it. We still have to wait for a magical answer (action) from now voodoo member MacMan.

So you're blaming me for him not releasing the sources along with the binaries?

 

I didn't nor could prevent him from releasing the source, on github or anywhere he prefers.

 

LOL I don't need to say that I'm impatient anymore, because that should have been pretty obvious by now already :D

 

Yeah yeah. I know. People are busy. Have other things to do. The more reason for a quick commit of your changes :P

I couldn't understand your last line, can you slow down a little?

Link to comment
Share on other sites
Time2Retire
Time2Retire
Posted
Posted
You said that I'm slow and lazy, then after the fact, you say you're not blaming me? that's weird.

No I didn't. Nowhere did I say (or imply) that you are slow or lazy. I said that things are going too slow.

 

p.s. Was thinking about adding a line from your last PM but I won't. You know why don't you :D

Link to comment
Share on other sites
Kabyl
Kabyl
Posted
Posted
p.s. Was thinking about adding a line from your last PM but I won't. You know why don't you :wacko:

You mean this line?

And it also shows how lazy I am.

 

No I didn't. Nowhere did I say (or imply) that you are slow or lazy. I said that things are going too slow.

What do you think one would take from each of these two lines?

 

I'm not blaming you for being an old lonely man.

 

I'm not saying you are an old lonely man.

 

Is my (understanding of) english that bad?

Link to comment
Share on other sites
^Andy^
^Andy^
Posted
Posted
Hey Andy,

 

I checked the patch and it seems you forgot the changes in pci.c/pci.h, these are necessary in ati.c.

 

Thanks!

 

Kabyl,

 

That should be fixed now and I have replaced the zip file on mediafire with the corrected code.

Hopefully it is now ok.

 

Thanks again for taking the time to look.

 

Regards

 

Andy.

Link to comment
Share on other sites
^Andy^
^Andy^
Posted
Posted
Hi Andy,

 

I noticed the bootloader does not have a GUI. Will there be a GUI implemented in the future?

 

Thanks for the bootloader.

 

All the best.

 

NSCXP2005

 

It should have a gui - Mine does (although thats probably because I have a theme in my extra folder).

 

P.S I'm {censored} at doing anything that requires artisitic talent so if it needs a theme its probbaly best you don't let me anywhere near it :rolleyes:

Link to comment
Share on other sites
Guest sincro77
Guest sincro77
Posted
Posted
Lion still booting with 64-bit kernel, even with arch=i386 in com.apple.Boot.plist :rolleyes:

 

I found a fix for this.. a little trick that seems to work for me.....

 

same issue it wants to boot into lp64 kernel even after adding i386 to boot plist..

 

when you see your drives in chameleon push " a then enter ...it will say command not found.. then

just hit enter again,.....voila ..boots into i386.. i need i386 for my builtin wifi to work on asus p5wh deluxe board. and quart extreme only wanted to be in i386 ,.. that might be cuz im using nvenabler thats not 64 .. i assume.

 

hope this trick works for others..

 

sincro77

Link to comment
Share on other sites
JBraddock
JBraddock
Posted
Posted
Would be nice to have an updated keylist (all keys available + how to use) or readme for the newest boot (v7).

I ask because that mixed Andy/.... sources. For example is busratio= key available, or whats now for 32 / 64 Bit ( i followed that arch=, non arch discuss and get confused) ?

I second this. Also, does anyone know if EnableC6State is being supported by RC5 or is it AnVaL specific. Also, with AnVaL, the following keys is enough for native speed step. Which keys should I be using with RC5?

<key>EnableC6State</key>
<string>Yes</string>
	<key>GeneratePStates</key>
<string>Yes</string>

Thanks,

Link to comment
Share on other sites
Time2Retire
Time2Retire
Posted
Posted
What do you think one would take from each of these two lines?

 

Is my (understanding of) english that bad?

Sorry but I fail to see the logic as to what these two lines have to do with the discussion at hand.

Link to comment
Share on other sites
rlf
rlf
Posted
Posted
Add diff V7

with the pci .c/.h changes...(from ^Andy^)

 

Fabio

Funny, for some reason, with diff V6 and V7, my VoodooPS2 won't work in Lion. However, with PC_EFI_10.6_Lion_Snow_V3 (used with Cham R2 750) it works just fine. Just saying.

 

Edit: never mind. If I boot from the Lion disk it works...if I boot from another disk, it doesn't. Obviously, there is more going on here.

Link to comment
Share on other sites
asapreta
asapreta
Posted
Posted

Another day, same problems with Adium, MSN ...

 

Here is a portion of the error report generated by Adium. MSN is the same:

 

Process:		 Adium [123]
Path:			/Applications/Adium.app/Contents/MacOS/Adium
Identifier:	  com.adiumX.adiumX
Version:		 1.4 (1.4)
Code Type:	   X86 (Native)
Parent Process:  launchd [111]

Date/Time:	   2011-05-03 23:07:54.221 +0000
OS Version:	  Mac OS X 10.7 (11A444d)
Report Version:  9

Interval Since Last Report:		  16139 sec
Crashes Since Last Report:		   23
Per-App Interval Since Last Report:  1349 sec
Per-App Crashes Since Last Report:   7
Anonymous UUID:					  AB8C7CE7-7BB2-405E-818D-E773B1879154

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

VM Regions Near 0:
--> __PAGEZERO			 0000000000000000-0000000000001000 [	4K] ---/--- SM=NUL  /Applications/Adium.app/Contents/MacOS/Adium
__TEXT				 0000000000001000-00000000001a0000 [ 1660K] r-x/rwx SM=COW  /Applications/Adium.app/Contents/MacOS/Adium

Application Specific Information:
objc[123]: garbage collection is OFF

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.QuickTime		   	0x0303c5f0 newMovieFromFileFromComponent + 0
1   com.apple.QuickTime		   	0x02fa8291 NewMovieFromFilePriv + 587
2   com.apple.QuickTime		   	0x02f81d7e NewMovieFromDataRefPriv_priv + 2148
3   com.apple.QuickTime		   	0x02f80d4e NewMovieFromProperties_priv + 5414
4   com.apple.QTKit			   	0x02d848ec -[QTMovie_QuickTime initWithAttributes:error:forParent:] + 5918
5   com.apple.QTKit			   	0x02d38d73 -[QTMovie initWithAttributes:error:] + 1058
6   com.apple.QTKit			   	0x02d77e1e -[QTMovie initWithDataReference:error:] + 181
7   com.apple.QTKit			   	0x02d780b8 -[QTMovie initWithFile:error:] + 209
8   com.adiumX.adiumX			 	0x001160eb 0x1000 + 1134827
9   com.adiumX.adiumX			 	0x0009567a 0x1000 + 607866
10  com.adiumX.adiumX			 	0x000e3d18 0x1000 + 929048
11  com.adiumX.adiumX			 	0x00083db5 0x1000 + 535989
12  Adium						 	0x0034fe03 -[AIContactObserverManager _informObserversOfObjectStatusChange:withKeys:silent:] + 344
13  Adium						 	0x0034f5f8 -[AIContactObserverManager listObjectStatusChanged:modifiedStatusKeys:silent:] + 64
14  Adium						 	0x00376634 -[AIListObject didModifyProperties:silent:] + 82
15  Adium						 	0x00372422 -[ESObjectWithProperties notifyOfChangedPropertiesSilently:] + 104
16  Adium						 	0x00375991 -[AIListObject notifyOfChangedPropertiesSilently:] + 60
17  com.apple.CoreFoundation		  0x034f6ca8 -[NSObject performSelector:withObject:withObject:] + 72
18  com.adiumX.AdiumPurple			0x002bb942 buddy_event_cb + 588
19  libpurple					 	0x00634a82 purple_marshal_VOID__POINTER + 40
20  libpurple					 	0x00634696 purple_signal_emit_vargs + 355
21  libpurple					 	0x0063452d purple_signal_emit + 125
22  libpurple					 	0x005eb1af purple_blist_update_buddy_status + 208
23  libpurple					 	0x0062a5f8 purple_prpl_got_user_status + 363
24  libpurple					 	0x006f3c03 msn_user_update + 152
25  libpurple					 	0x006e2ba7 nln_cmd + 451
26  libpurple					 	0x006cb0f1 msn_cmdproc_process_cmd + 425
27  libpurple					 	0x006cb19d msn_cmdproc_process_cmd_text + 96
28  libpurple					 	0x006e8906 msn_servconn_process_data + 238
29  libpurple					 	0x006e87dd read_cb + 438
30  com.apple.CoreFoundation		  0x0343a8db __CFSocketPerformV0 + 1163
31  com.apple.CoreFoundation		  0x034b526f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
32  com.apple.CoreFoundation		  0x033f7a66 __CFRunLoopDoSources0 + 246
33  com.apple.CoreFoundation		  0x033f73b8 __CFRunLoopRun + 1112
34  com.apple.CoreFoundation		  0x033f6b4c CFRunLoopRunSpecific + 332
35  com.apple.CoreFoundation		  0x033f69f8 CFRunLoopRunInMode + 120
36  com.apple.HIToolbox		   	0x06967af3 RunCurrentEventLoopInMode + 318
37  com.apple.HIToolbox		   	0x069678bb ReceiveNextEventCommon + 381
38  com.apple.HIToolbox		   	0x0696772a BlockUntilNextEventMatchingListInMode + 88
39  com.apple.AppKit				  0x03d37e68 _DPSNextEvent + 678
40  com.apple.AppKit				  0x03d376d4 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
41  com.apple.AppKit				  0x03cf9542 -[NSApplication run] + 897
42  com.apple.AppKit				  0x03cf1698 NSApplicationMain + 1047
43  com.adiumX.adiumX			 	0x0000382e 0x1000 + 10286

 

Any clues?

Link to comment
Share on other sites
ErmaC
ErmaC
Posted
  • Author
Posted

Hi people!

I have a question...

 

Into the pci.h file (i386/libsaio/pci.h)

relate with this commit by valv --> http://forge.voodooprojects.org/p/chameleo...rce/commit/595/

google is my friend..

 

#define PCI_CLASS_CRYPT_ENTERTAINMENT 0x1010

should be ????

I search for this info but all say 1010 :(

 

#define PCI_VENDOR_ID_AMD 0x1002

should be 1022 --> http://www.pcidatabase.com/vendor_details.php?id=269

 

Fabio

Link to comment
Share on other sites
^Andy^
^Andy^
Posted
Posted
Hi people!

I have a question...

 

Into the pci.h file (i386/libsaio/pci.h)

relate with this commit by valv --> http://forge.voodooprojects.org/p/chameleo...rce/commit/595/

google is my friend..

 

#define PCI_CLASS_CRYPT_ENTERTAINMENT 0x1010

should be ????

I search for this info but all say 1010 :P

 

#define PCI_VENDOR_ID_AMD 0x1002

should be 1022 --> http://www.pcidatabase.com/vendor_details.php?id=269

 

Fabio

 

Yeah I wasn't sure about those either :( I think I will change them back because most other builds have them set that way. Gives me something to fiddle with tonight I guess lol.

Link to comment
Share on other sites
^Andy^
^Andy^
Posted
Posted
This may or may not be relevant, but ATI (now owned by AMD) has been 1002 and the Radeon video cards are identified with 1002 (unless they changed recently). 1022 is AMD and I would imagine that it applies to other AMD hardware like maybe CPU's, etc.

 

Just looked at the code - the AMD entry isn't used as far as I can tell so I will either delete the definition or change it back to 1022 for consistency.

 

Also looks like #define PCI_CLASS_CRYPT_ENTERTAINMENT 0x1010 should be correct.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...