You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(22) |
Dec
(27) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(108) |
Feb
(179) |
Mar
(182) |
Apr
(199) |
May
(67) |
Jun
(132) |
Jul
(80) |
Aug
(74) |
Sep
(139) |
Oct
(51) |
Nov
(34) |
Dec
(54) |
2003 |
Jan
(44) |
Feb
(37) |
Mar
(95) |
Apr
(68) |
May
(54) |
Jun
(145) |
Jul
(116) |
Aug
(45) |
Sep
(7) |
Oct
(95) |
Nov
(38) |
Dec
(59) |
2004 |
Jan
(53) |
Feb
(117) |
Mar
(52) |
Apr
(30) |
May
(75) |
Jun
(32) |
Jul
(60) |
Aug
(132) |
Sep
(44) |
Oct
(39) |
Nov
(58) |
Dec
(13) |
2005 |
Jan
(64) |
Feb
(20) |
Mar
(12) |
Apr
(76) |
May
(12) |
Jun
(11) |
Jul
(16) |
Aug
|
Sep
(23) |
Oct
(6) |
Nov
(20) |
Dec
(27) |
2006 |
Jan
(2) |
Feb
(10) |
Mar
(7) |
Apr
|
May
(8) |
Jun
(27) |
Jul
(39) |
Aug
(46) |
Sep
(35) |
Oct
(34) |
Nov
(7) |
Dec
|
2007 |
Jan
(4) |
Feb
(7) |
Mar
(3) |
Apr
|
May
(8) |
Jun
(6) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(5) |
2008 |
Jan
(12) |
Feb
(42) |
Mar
(12) |
Apr
(27) |
May
(24) |
Jun
(6) |
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
(3) |
Feb
|
Mar
(6) |
Apr
|
May
(5) |
Jun
|
Jul
(6) |
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
(5) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(18) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
(12) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(23) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(4) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
2016 |
Jan
(7) |
Feb
(9) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(17) |
From: Mark M. <msm...@ii...> - 2013-05-23 21:01:06
|
On 24/05/2013 2:45 AM, Lawrence Sebald wrote: > *cough* *cough* Ahem! Is this thing on? Ah, good! I'm listening! ;) Nice work! Regards, -- | Mark McDougall | "Electrical Engineers do it | <http://members.iinet.net.au/~msmcdoug> | with less resistance!" |
From: Groepaz <gr...@gm...> - 2013-05-23 19:17:20
|
On Thursday 23 May 2013, Lawrence Sebald wrote: > *cough* *cough* Ahem! Is this thing on? Ah, good! > > So, just in case there is anyone on this list that isn't on the commits > list and who hasn't noticed otherwise, I wanted to announce that after ten > long years, KOS finally sees a new point release. > > It has been a long road, and pretty much everything has changed since 2003 > when 1.2.0 came out, so this new release is 2.0.0 to reflect that reality. > > There's far too much that has changed to detail everything, so just check > out the release and the changelog contained therein. ;-) wow i am still subscribed =) are there any ready-to-burn isos of any dreamcast stuff made in the past year(s) around? (i dont have a development environment set up atm... but i can burn a cd, hopefully =D) -- http://www.hitmen-console.org http://magicdisk.untergrund.net http://www.pokefinder.org http://ftp.pokefinder.org volltrunkenheit - Ãähnlicher Begriff: vollkommenheit <wikipedia> |
From: James S. <jam...@gm...> - 2013-05-23 16:55:26
|
Wow. Congratulations on the release. On Thu, May 23, 2013 at 12:45 PM, Lawrence Sebald <ljs...@us...> wrote: > *cough* *cough* Ahem! Is this thing on? Ah, good! > > So, just in case there is anyone on this list that isn't on the commits list and who hasn't noticed otherwise, I wanted to announce that after ten long years, KOS finally sees a new point release. > > It has been a long road, and pretty much everything has changed since 2003 when 1.2.0 came out, so this new release is 2.0.0 to reflect that reality. > > There's far too much that has changed to detail everything, so just check out the release and the changelog contained therein. ;-) > > - Lawrence -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59 |
From: Lawrence S. <ljs...@us...> - 2013-05-23 16:46:01
|
*cough* *cough* Ahem! Is this thing on? Ah, good! So, just in case there is anyone on this list that isn't on the commits list and who hasn't noticed otherwise, I wanted to announce that after ten long years, KOS finally sees a new point release. It has been a long road, and pretty much everything has changed since 2003 when 1.2.0 came out, so this new release is 2.0.0 to reflect that reality. There's far too much that has changed to detail everything, so just check out the release and the changelog contained therein. ;-) - Lawrence |
From: Christian G. <ko...@ya...> - 2013-05-08 22:37:53
|
Hi, in case you're wondering about the "resend" in the subject, don't fear, you haven't missed a mail. Here's the original mail: http://sourceforge.net/mailarchive/forum.php?thread_name=246d679a0512191323g9be7b2fn408b0ada9bf7ed13%40mail.gmail.com&forum_name=cadcdev-kallistios There's still no way to detect if a file was successfully written to the VMU, so I've updated the patch to the current version. On the way I've also reworked it a bit, now close() returns 0 or -1 and more detailed information can be obtained by inspecting 'errno'. If nobody objects, I will check in the patch within the next few days. regards, chris |
From: Lawrence S. <ljs...@us...> - 2013-04-30 15:26:51
|
On Apr 30, 2013, at 6:52 AM, Christian Groessler <ko...@ya...> wrote: > Thanks. That was the problem. I've updated the plasma demo with the cache flush. Good to hear that my gut instinct was right on that. Thanks for testing that out and updating it. > Another question, about the "twiddling" of textures: I see what the macros do, but is there any documentation of description of it? There's a brief description of the algorithm itself at the top of this piece of code: http://cadcdev.sourceforge.net/softprj/twiddle.c Plus, that should be a little bit easier to follow than the macros, I think. - Lawrence |
From: Christian G. <ko...@ya...> - 2013-04-30 10:52:54
|
--- Lawrence Sebald <ljs...@us...> schrieb am Mo, 29.4.2013: > It has been quite quiet here for a > long time... There are other, more active places to discuss > KOS-related stuff, including the #dreamcastdev channel on > the Freenode IRC network. I'll check it out. > On the subject of the plasma example, I'm going to take a > guess that it is because the data hasn't been flushed from > the cache before the DMA tries to transfer it. You need to > flush it all out of the dcache before it'll work properly. Thanks. That was the problem. I've updated the plasma demo with the cache flush. Another question, about the "twiddling" of textures: I see what the macros do, but is there any documentation of description of it? regards, chris |
From: Lawrence S. <ljs...@us...> - 2013-04-29 16:06:02
|
It has been quite quiet here for a long time... There are other, more active places to discuss KOS-related stuff, including the #dreamcastdev channel on the Freenode IRC network. On the subject of the plasma example, I'm going to take a guess that it is because the data hasn't been flushed from the cache before the DMA tries to transfer it. You need to flush it all out of the dcache before it'll work properly. - Lawrence On Apr 29, 2013, at 8:27 AM, Christian Groessler <ko...@ya...> wrote: > Hi, > > this mailing list appears to be quite abandoned, but still I see occasional commits to the repository. > > So, my question, is the mailing list here still the primary place for discussions about KOS development or is there another forum in the meanwhile? > > And, anoher question: > > I've tried the plasma sample (examples/dreamcast/pvr/plasma) and in line 102 in plasma.c there is a comment "Switch these around to try out texture DMA". > I've switched them around (commented the pvr_txr_load line and uncommented the pvr_txr_load_dma line, btw. there were missing parameters to the call to pvr_txr_load_dma), but then I get flickering garbage overlaid over the plasma display. > It looks like every second frame displays garbage. > > Could someone with more knowledge than me look into it and tell me what is wrong? I couldn't manage to fix it myself to use DMA correctly. > > regards, > chris > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > cadcdev-kallistios mailing list > cad...@li... > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios |
From: Christian G. <ko...@ya...> - 2013-04-29 12:27:16
|
Hi, this mailing list appears to be quite abandoned, but still I see occasional commits to the repository. So, my question, is the mailing list here still the primary place for discussions about KOS development or is there another forum in the meanwhile? And, anoher question: I've tried the plasma sample (examples/dreamcast/pvr/plasma) and in line 102 in plasma.c there is a comment "Switch these around to try out texture DMA". I've switched them around (commented the pvr_txr_load line and uncommented the pvr_txr_load_dma line, btw. there were missing parameters to the call to pvr_txr_load_dma), but then I get flickering garbage overlaid over the plasma display. It looks like every second frame displays garbage. Could someone with more knowledge than me look into it and tell me what is wrong? I couldn't manage to fix it myself to use DMA correctly. regards, chris |
From: Joseph F. <jlf...@gm...> - 2012-07-08 02:50:38
|
On Thu, Jul 5, 2012 at 10:10 PM, Lawrence Sebald <blu...@gm...> wrote: > I'm guessing by the SF link you mean the one on the Code > Git page on the sf.net project page? If so, there's nothing I can do about that, unfortunately (at least as far as I know). > > The correct link is listed on the KOS website itself though. ;) I do need to update that page since kos-ports is now in Git as well though... Yes, that was the problem. The SF link I was using was git clone git://cadcdev.git.sourceforge.net/gitroot/cadcdev/cadcdev which fail. The one you gave worked fine. Thanks! |
From: Lawrence S. <blu...@gm...> - 2012-07-06 04:10:33
|
I'm guessing by the SF link you mean the one on the Code > Git page on the sf.net project page? If so, there's nothing I can do about that, unfortunately (at least as far as I know). The correct link is listed on the KOS website itself though. ;) I do need to update that page since kos-ports is now in Git as well though... - Lawrence On Jul 6, 2012, at 12:07 AM, qu...@ya... wrote: > Same thing happened to me. SF has the link on our front page wrong. It says 'cadcdev/cadcdev' > > Sent from my Android phone on T-Mobile. America’s first nationwide 4G network. > > ----- Reply message ----- > From: "Lawrence Sebald" <blu...@gm...> > To: <cad...@li...> > Subject: [KOS] Git Repository and other news > Date: Thu, Jul 5, 2012 11:09 pm > > > It seems to be working fine for me, like so: > git clone git://cadcdev.git.sourceforge.net/gitroot/cadcdev/KallistiOS > > - Lawrence > > On Jul 5, 2012, at 11:07 PM, Joseph Fenton wrote: > > > On Thu, Jul 5, 2012 at 6:52 PM, Lawrence Sebald <blu...@gm...> wrote: > > > >> For various reasons, no it does not. > > > > No problem, just checking. Is the repo locked or something? When I try > > to clone the git repo, I get > > > > fatal: The remote end hung up unexpectedly > > > > Maybe I'm just using the wrong url... > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > cadcdev-kallistios mailing list > > cad...@li... > > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > cadcdev-kallistios mailing list > cad...@li... > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ > cadcdev-kallistios mailing list > cad...@li... > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios |
From: <qu...@ya...> - 2012-07-06 04:07:08
|
Same thing happened to me. SF has the link on our front page wrong. It says 'cadcdev/cadcdev' Sent from my Android phone on T-Mobile. America’s first nationwide 4G network. ----- Reply message ----- From: "Lawrence Sebald" <blu...@gm...> To: <cad...@li...> Subject: [KOS] Git Repository and other news Date: Thu, Jul 5, 2012 11:09 pm It seems to be working fine for me, like so: git clone git://cadcdev.git.sourceforge.net/gitroot/cadcdev/KallistiOS - Lawrence On Jul 5, 2012, at 11:07 PM, Joseph Fenton wrote: > On Thu, Jul 5, 2012 at 6:52 PM, Lawrence Sebald <blu...@gm...> wrote: > >> For various reasons, no it does not. > > No problem, just checking. Is the repo locked or something? When I try > to clone the git repo, I get > > fatal: The remote end hung up unexpectedly > > Maybe I'm just using the wrong url... > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > cadcdev-kallistios mailing list > cad...@li... > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ cadcdev-kallistios mailing list cad...@li... https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios |
From: Lawrence S. <blu...@gm...> - 2012-07-06 03:10:05
|
It seems to be working fine for me, like so: git clone git://cadcdev.git.sourceforge.net/gitroot/cadcdev/KallistiOS - Lawrence On Jul 5, 2012, at 11:07 PM, Joseph Fenton wrote: > On Thu, Jul 5, 2012 at 6:52 PM, Lawrence Sebald <blu...@gm...> wrote: > >> For various reasons, no it does not. > > No problem, just checking. Is the repo locked or something? When I try > to clone the git repo, I get > > fatal: The remote end hung up unexpectedly > > Maybe I'm just using the wrong url... > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > cadcdev-kallistios mailing list > cad...@li... > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios |
From: Joseph F. <jlf...@gm...> - 2012-07-06 03:07:19
|
On Thu, Jul 5, 2012 at 6:52 PM, Lawrence Sebald <blu...@gm...> wrote: > For various reasons, no it does not. No problem, just checking. Is the repo locked or something? When I try to clone the git repo, I get fatal: The remote end hung up unexpectedly Maybe I'm just using the wrong url... |
From: Lawrence S. <blu...@gm...> - 2012-07-06 00:52:34
|
For various reasons, no it does not. - Lawrence On Jul 4, 2012, at 12:05 AM, Joseph Fenton wrote: > I'm still here... been a bit busy earlier helping my dad... one > question: any time frame on SD card support in the official repo? > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > cadcdev-kallistios mailing list > cad...@li... > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios |
From: Joseph F. <jlf...@gm...> - 2012-07-04 04:05:44
|
I'm still here... been a bit busy earlier helping my dad... one question: any time frame on SD card support in the official repo? |
From: Lawrence S. <blu...@gm...> - 2012-06-15 17:38:19
|
I don't necessarily agree with just deleting all the old stuff in the KOS webspace. A lot of it holds a lot of the history of the Dreamcast homebrew community in general, which would be something I wouldn't want to see deleted. That said, the website does indeed need a lot of work. I intend to start working on that kind of stuff soon. I'm glad to see there are still a few people around on the mailing list at least. :) If you guys haven't been around IRC, I'd recommend popping into the IRC channel every once in a while, as that's where most of the KOS-related discussions have taken place the past few years. - Lawrence On Jun 14, 2012, at 7:18 PM, Torsten Giebl wrote: > Hello Lawrence ! > > > Thank you, thousand times, for keeping this project alive. > I read all your commit emails in the past years. > > Personally i would delete everything that does not work actually > from the SVN repository. I hate nothing more than finding sources > that do not work anymore. > > In the future, if somebody wants to start > working on them again, they can always still get them from SVN. > If you want to use GIT in the future, fine. > > Also personally i would delete all the actual sites from the KOS > project and create one or two pages, how to run it on the DC and good. > Most of the other pages are so horribly outdated, that they do not serve > any purpose anymore. > > > CU > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > cadcdev-kallistios mailing list > cad...@li... > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios |
From: Torsten G. <wi...@sy...> - 2012-06-15 04:06:31
|
Hello Lawrence ! Thank you, thousand times, for keeping this project alive. I read all your commit emails in the past years. Personally i would delete everything that does not work actually from the SVN repository. I hate nothing more than finding sources that do not work anymore. In the future, if somebody wants to start working on them again, they can always still get them from SVN. If you want to use GIT in the future, fine. Also personally i would delete all the actual sites from the KOS project and create one or two pages, how to run it on the DC and good. Most of the other pages are so horribly outdated, that they do not serve any purpose anymore. CU |
From: James S. <jam...@gm...> - 2012-06-14 22:57:32
|
I'm still subscribed. In fact, I had been wondering if anything was still going on with this project. Thank you for the update. On Thursday, June 14, 2012, Lawrence Sebald wrote: > Its been a while since anyone's used this list, hasn't it? Anyway, just in > case there are some people out there still interested in things going on > with KOS that haven't found their way to IRC (#dreamcastdev on freenode), I > wanted to send out a quick update email about what's been going on. > > First and foremost, after a discussion amongst those of us active on the > IRC channel, we decided to migrate the source code repository from SVN to > Git. The central repository is still hosted on Sourceforge, just in Git now > instead of Subversion. As of right now, KallistiOS, dcload-ip, and > dcload-serial have been migrated. We're still working out exactly how we're > going to deal with kos-ports, so for the time being that will be staying in > Subversion. All the other pieces in the SVN repo (slinkie, navi, tiki and > the ps2 stuff) will likely stay there as well, unless someone wants to step > up and maintain those pieces (I'd be happy to move them to Git if that is > the case). The SVN repo isn't going anywhere, it just won't be updated any > more for those things that have been moved to the Git repo. > > All commit mails still go to the cadcdev-svn-commits list, so if you're > subscribed there, you should have seen the first few mails from Git the > other day. > > Speaking of maintaining bits and pieces, is anyone interested in keeping > around and maintaining the non-Dreamcast versions of KOS (gba, x86, ps2)? > If not, they will probably be removed from the Git repo in the future. It > doesn't really make much sense to keep them around if they aren't > maintained and probably don't work anymore, in my eyes. > > With regard to KOS itself, I put up a roadmap on the KOS website some time > ago for where I wanted to try to direct future development toward an > eventual release (http://gamedev.allusion.net/softprj/kos/roadmap.php). > As of now, most of the realistic things I had thought up for that roadmap > have been taken care of, other than documentation and testing. Its been a > long while coming, but its my opinion that we're to the point where we > might want to start considering a full release for the first time in a long > while. I'd be interested to hear if anyone else out there has any ideas of > what should be worked on prior to a release. Also, in general, I'm > interested to see who's still around on this list in the first place. ;-) > > Anyway, that's all I have for now, so I guess I'll cut it off here. > - Lawrence > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > cadcdev-kallistios mailing list > cad...@li... <javascript:;> > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios > -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59 |
From: Lawrence S. <blu...@gm...> - 2012-06-14 22:53:02
|
Its been a while since anyone's used this list, hasn't it? Anyway, just in case there are some people out there still interested in things going on with KOS that haven't found their way to IRC (#dreamcastdev on freenode), I wanted to send out a quick update email about what's been going on. First and foremost, after a discussion amongst those of us active on the IRC channel, we decided to migrate the source code repository from SVN to Git. The central repository is still hosted on Sourceforge, just in Git now instead of Subversion. As of right now, KallistiOS, dcload-ip, and dcload-serial have been migrated. We're still working out exactly how we're going to deal with kos-ports, so for the time being that will be staying in Subversion. All the other pieces in the SVN repo (slinkie, navi, tiki and the ps2 stuff) will likely stay there as well, unless someone wants to step up and maintain those pieces (I'd be happy to move them to Git if that is the case). The SVN repo isn't going anywhere, it just won't be updated any more for those things that have been moved to the Git repo. All commit mails still go to the cadcdev-svn-commits list, so if you're subscribed there, you should have seen the first few mails from Git the other day. Speaking of maintaining bits and pieces, is anyone interested in keeping around and maintaining the non-Dreamcast versions of KOS (gba, x86, ps2)? If not, they will probably be removed from the Git repo in the future. It doesn't really make much sense to keep them around if they aren't maintained and probably don't work anymore, in my eyes. With regard to KOS itself, I put up a roadmap on the KOS website some time ago for where I wanted to try to direct future development toward an eventual release (http://gamedev.allusion.net/softprj/kos/roadmap.php). As of now, most of the realistic things I had thought up for that roadmap have been taken care of, other than documentation and testing. Its been a long while coming, but its my opinion that we're to the point where we might want to start considering a full release for the first time in a long while. I'd be interested to hear if anyone else out there has any ideas of what should be worked on prior to a release. Also, in general, I'm interested to see who's still around on this list in the first place. ;-) Anyway, that's all I have for now, so I guess I'll cut it off here. - Lawrence |
From: Caleb C. <cal...@gm...> - 2010-12-23 05:29:49
|
So I found all the libs in question in my /lib directory. I updated my Makefile.cfg to use: ... *# cygwin** **# these must point to your sh-elf bfd, not the system one** **BFDLIB = -L/usr/local/dc/i686-pc-cygwin/sh-elf/lib -lbfd -L/lib -liberty -lintl -lz** **BFDINCLUDE = /usr/local/dc/i686-pc-cygwin/sh-elf/include** * *...* * * Ran a "make clean" just to be sure and then another "make" and here is what I'm getting: *Caleb@Caleb-TouchPC/cygdrive/c/Users/Caleb/Dreamcast/Development/dcload-ip-1.0.4 ** **$ make** **make -C host-src** **make[1]: Entering directory `/cygdrive/c/Users/Caleb/Dreamcast/Development/dcload-ip-1.0.4/host-src'** **make -C tool** **make[2]: Entering directory `/cygdrive/c/Users/Caleb/Dreamcast/Development/dcload-ip-1.0.4/host-src/tool' ** **gcc -O2 -D_WIN32 -DDCLOAD_VERSION=\"1.0.4\" -DDREAMCAST_IP=\"000.000.000.000\" -DHAVE_GETOPT -I/usr/local/dc/i686-pc-cyg ** **win/sh-elf/include -o dc-tool.o -c dc-tool.c** **In file included from dc-tool.c:42:** **syscalls.h:68: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[4]’** **syscalls.h:75: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[4]’** **syscalls.h:78: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[1]’** **syscalls.h:82: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[4]’** **syscalls.h:87: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[4]’** **syscalls.h:89: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[1]’** **syscalls.h:93: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[4]’** **syscalls.h:94: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[1]’** **syscalls.h:98: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[4]’** **syscalls.h:102: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[1]’** **In file included from dc-tool.c:44:** **commands.h:5: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[4]’** **commands.h:8: warning: ‘packed’ attribute ignored for field of type ‘unsigned char[1]’** **dc-tool.c:185: warning: ‘optarg’ redeclared without dllimport attribute: previous dllimport ignored** **dc-tool.c: In function ‘upload’:** **dc-tool.c:446: error: ‘asection’ has no member named ‘_raw_size’** **dc-tool.c:447: error: ‘asection’ has no member named ‘_raw_size’** **dc-tool.c:448: error: ‘asection’ has no member named ‘_raw_size’** **dc-tool.c:449: error: ‘asection’ has no member named ‘_raw_size’** **dc-tool.c:450: error: ‘asection’ has no member named ‘_raw_size’** **dc-tool.c:452: error: ‘asection’ has no member named ‘_raw_size’** **make[2]: *** [dc-tool.o] Error 1** **make[2]: Leaving directory `/cygdrive/c/Users/Caleb/Dreamcast/Development/dcload-ip-1.0.4/host-src/tool' ** **make[1]: *** [tool] Error 2** **make[1]: Leaving directory `/cygdrive/c/Users/Caleb/Dreamcast/Development/dcload-ip-1.0.4/host-src'** **make: *** [host-src] Error 2** * * * It doesn't look like the host-tool is even using the BFDLIBs so maybe something else is wrong?* * * * ~Caleb On Wed, Dec 22, 2010 at 3:45 PM, Harley Laue <los...@gm...>wrote: > On Wed, Dec 22, 2010 at 3:31 PM, Caleb Cittadino > <cal...@gm...> wrote: > > I think my bfd items are here: > > > > /usr/local/dc/i686-pc-cygwin/sh-elf/lib > > /usr/local/dc/i686-pc-cygwin/sh-elf/include > > Yeah, you're right. Those are the directories you should be using for > BFDLIB and BFDINCLUDE The Makefile.cfg I included wasn't quite right. > Glad you spotted the correct directories on your own :) > > > It looks like the Makefile.cfg is looking for more libs than I have (for > the > > cygwin specific block): > > > > "BFDLIB = -L/usr/local/dc/i686-pc-cygwin/sh-elf/lib -lbfd -liberty > > -lintl" > > > > Should I just add an extra directory to scan with -L so that iberty gets > > picked up in the other location or is that the wrong lib? Also what > about > > the third lib listed up there: "intl". Is that one still needed for > cygwin? > > You should also have an iberty in /usr/lib, > /lib,/usr/i686-pc-cygwin/lib or someplace similar. That's actually > what should then get picked up by the compiler for that portion of the > compilation process (which is what you want.) intl may not be needed, > and z(lib) might be needed to be added to that line. I can't say for > sure, but that should get you pretty close. > > Just a bit of info about dcload, it consists of two programs, a host > and a target program. The host program is run on your machine to send > executables to the target (the Dreamcast.) The libbfd from sh-elf is > required for the host to know how to work with the target elf format > at a low level. > > > On Wed, Dec 22, 2010 at 1:04 PM, Harley Laue <los...@gm... > > > > wrote: > >> > >> Caleb Cittadino wrote: > >> > Running "./buildcross -dc -k" did the trick! > >> > >> Ooops, I made a slight typo when I said ./buildcross dc -k, I should > >> have written ./buildcross.sh dreamcast -k > >> -dc -k most likely built kos&kos-ports then rebuilt kos&kos-ports. Not > >> a huge deal besides taking a bit more time. :) > >> > >> > Now I am just trying to find a way to test code. It seems the best > way > >> > is > >> > to just send the elf over the network to the dc using "dcload-ip" > >> > correct? > >> > I pulled down the latest one (1.0.4 from 2003) and am trying to get > it > >> > built now. Running into some issues with the bfd libs though. Anyone > >> > use > >> > something different or better that is known to work with the latest > >> > tools? > >> > >> If you have a BBA dcload-ip is absolutely the way to go. It's not > >> exactly the easiest thing to build because it requires that libbdf > >> from sh-elf be installed and then you have to edit the Makefile.cfg > >> for dcload to point to the installed location of that lib/include. The > >> other thing that might be useful for you to change in the Makefile.cfg > >> is the IP of the Dreamcast. > >> > >> There is one other BBA loader that I can think of off the top of my > >> head, but AFAIK it's totally unmaintained (not to mention dcload is > >> much more robust in comparison.) Anyways the loader I'm thinking of is > >> IP upload slave (http://mc.pp.se/dc/ipslave.html) which was one of the > >> first Dreamcast BBA loaders. > >> > >> Attached is a Makefile.cfg that worked for me on a Linux machine that > >> I used buildcross with. You'll probably still need to edit it a bit, > >> but it should be much closer to what you need. > > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, > and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Cadcdev-kallistios mailing list > Cad...@li... > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios > |
From: Harley L. <los...@gm...> - 2010-12-22 22:45:27
|
On Wed, Dec 22, 2010 at 3:31 PM, Caleb Cittadino <cal...@gm...> wrote: > I think my bfd items are here: > > /usr/local/dc/i686-pc-cygwin/sh-elf/lib > /usr/local/dc/i686-pc-cygwin/sh-elf/include Yeah, you're right. Those are the directories you should be using for BFDLIB and BFDINCLUDE The Makefile.cfg I included wasn't quite right. Glad you spotted the correct directories on your own :) > It looks like the Makefile.cfg is looking for more libs than I have (for the > cygwin specific block): > > "BFDLIB = -L/usr/local/dc/i686-pc-cygwin/sh-elf/lib -lbfd -liberty > -lintl" > > Should I just add an extra directory to scan with -L so that iberty gets > picked up in the other location or is that the wrong lib? Also what about > the third lib listed up there: "intl". Is that one still needed for cygwin? You should also have an iberty in /usr/lib, /lib,/usr/i686-pc-cygwin/lib or someplace similar. That's actually what should then get picked up by the compiler for that portion of the compilation process (which is what you want.) intl may not be needed, and z(lib) might be needed to be added to that line. I can't say for sure, but that should get you pretty close. Just a bit of info about dcload, it consists of two programs, a host and a target program. The host program is run on your machine to send executables to the target (the Dreamcast.) The libbfd from sh-elf is required for the host to know how to work with the target elf format at a low level. > On Wed, Dec 22, 2010 at 1:04 PM, Harley Laue <los...@gm...> > wrote: >> >> Caleb Cittadino wrote: >> > Running "./buildcross -dc -k" did the trick! >> >> Ooops, I made a slight typo when I said ./buildcross dc -k, I should >> have written ./buildcross.sh dreamcast -k >> -dc -k most likely built kos&kos-ports then rebuilt kos&kos-ports. Not >> a huge deal besides taking a bit more time. :) >> >> > Now I am just trying to find a way to test code. It seems the best way >> > is >> > to just send the elf over the network to the dc using "dcload-ip" >> > correct? >> > I pulled down the latest one (1.0.4 from 2003) and am trying to get it >> > built now. Running into some issues with the bfd libs though. Anyone >> > use >> > something different or better that is known to work with the latest >> > tools? >> >> If you have a BBA dcload-ip is absolutely the way to go. It's not >> exactly the easiest thing to build because it requires that libbdf >> from sh-elf be installed and then you have to edit the Makefile.cfg >> for dcload to point to the installed location of that lib/include. The >> other thing that might be useful for you to change in the Makefile.cfg >> is the IP of the Dreamcast. >> >> There is one other BBA loader that I can think of off the top of my >> head, but AFAIK it's totally unmaintained (not to mention dcload is >> much more robust in comparison.) Anyways the loader I'm thinking of is >> IP upload slave (http://mc.pp.se/dc/ipslave.html) which was one of the >> first Dreamcast BBA loaders. >> >> Attached is a Makefile.cfg that worked for me on a Linux machine that >> I used buildcross with. You'll probably still need to edit it a bit, >> but it should be much closer to what you need. |
From: Caleb C. <cal...@gm...> - 2010-12-22 21:31:38
|
I think my bfd items are here: /usr/local/dc/i686-pc-cygwin/sh-elf/lib /usr/local/dc/i686-pc-cygwin/sh-elf/include This is what I see build in those locations: *Caleb@Caleb-TouchPC/cygdrive/c/Users/Caleb/Dreamcast/Development/dcload-ip-1.0.4 ** **$ ll /usr/local/dc/i686-pc-cygwin/sh-elf/include/** **total 260** **drwxr-xr-x+ 1 Caleb None 0 2010-12-21 11:11 .** **drwxr-xr-x+ 1 Caleb None 0 2010-12-21 11:10 ..** **-rw-r--r-- 1 Caleb None 13857 2010-12-21 11:11 ansidecl.h** **-rw-r--r-- 1 Caleb None 192401 2010-12-21 11:11 bfd.h** **-rw-r--r-- 1 Caleb None 29506 2010-12-21 11:11 bfdlink.h** **-rw-r--r-- 1 Caleb None 16736 2010-12-21 11:10 dis-asm.h** **-rw-r--r-- 1 Caleb None 1902 2010-12-21 11:11 symcat.h** * * * * Caleb@Caleb-TouchPC/cygdrive/c/Users/Caleb/Dreamcast/Development/dcload-ip-1.0.4 $ ll /usr/local/dc/i686-pc-cygwin/sh-elf/lib/ total 5028 drwxr-xr-x+ 1 Caleb None 4096 2010-12-21 11:11 . drwxr-xr-x+ 1 Caleb None 0 2010-12-21 11:10 .. -rw-r--r-- 1 Caleb None 4754356 2010-12-21 11:11 libbfd.a -rwxr-xr-x 1 Caleb None 893 2010-12-21 11:11 libbfd.la -rw-r--r-- 1 Caleb None 377454 2010-12-21 11:10 libopcodes.a -rwxr-xr-x 1 Caleb None 901 2010-12-21 11:10 libopcodes.la * * * It looks like the Makefile.cfg is looking for more libs than I have (for the cygwin specific block):* * *"BFDLIB = -L/usr/local/dc/i686-pc-cygwin/sh-elf/lib -lbfd -liberty -lintl"* * * I actually see the iberty lib here: *Caleb@Caleb-TouchPC/cygdrive/c/Users/Caleb/Dreamcast/Development/dcload-ip-1.0.4 ** **$ ll /usr/local/dc/lib** **total 588** **drwxr-xr-x+ 1 Caleb None 0 2010-12-21 18:18 .** **drwxr-xr-x+ 1 Caleb None 4096 2010-12-21 16:49 ..** **drwxr-xr-x+ 1 Caleb None 0 2010-12-21 18:17 gcc** **-rw-r--r-- 1 Caleb None 597228 2010-12-21 18:18 libiberty.a** * * * Should I just add an extra directory to scan with -L so that iberty gets picked up in the other location or is that the wrong lib? Also what about the third lib listed up there: "intl". Is that one still needed for cygwin? * * * * ~Caleb On Wed, Dec 22, 2010 at 1:04 PM, Harley Laue <los...@gm...>wrote: > Caleb Cittadino wrote: > > Running "./buildcross -dc -k" did the trick! > > Ooops, I made a slight typo when I said ./buildcross dc -k, I should > have written ./buildcross.sh dreamcast -k > -dc -k most likely built kos&kos-ports then rebuilt kos&kos-ports. Not > a huge deal besides taking a bit more time. :) > > > Now I am just trying to find a way to test code. It seems the best way > is > > to just send the elf over the network to the dc using "dcload-ip" > correct? > > I pulled down the latest one (1.0.4 from 2003) and am trying to get it > > built now. Running into some issues with the bfd libs though. Anyone > use > > something different or better that is known to work with the latest > tools? > > If you have a BBA dcload-ip is absolutely the way to go. It's not > exactly the easiest thing to build because it requires that libbdf > from sh-elf be installed and then you have to edit the Makefile.cfg > for dcload to point to the installed location of that lib/include. The > other thing that might be useful for you to change in the Makefile.cfg > is the IP of the Dreamcast. > > There is one other BBA loader that I can think of off the top of my > head, but AFAIK it's totally unmaintained (not to mention dcload is > much more robust in comparison.) Anyways the loader I'm thinking of is > IP upload slave (http://mc.pp.se/dc/ipslave.html) which was one of the > first Dreamcast BBA loaders. > > Attached is a Makefile.cfg that worked for me on a Linux machine that > I used buildcross with. You'll probably still need to edit it a bit, > but it should be much closer to what you need. > > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, > and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Cadcdev-kallistios mailing list > Cad...@li... > https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios > > |
From: Harley L. <los...@gm...> - 2010-12-22 20:05:06
|
Caleb Cittadino wrote: > Running "./buildcross -dc -k" did the trick! Ooops, I made a slight typo when I said ./buildcross dc -k, I should have written ./buildcross.sh dreamcast -k -dc -k most likely built kos&kos-ports then rebuilt kos&kos-ports. Not a huge deal besides taking a bit more time. :) > Now I am just trying to find a way to test code. It seems the best way is > to just send the elf over the network to the dc using "dcload-ip" correct? > I pulled down the latest one (1.0.4 from 2003) and am trying to get it > built now. Running into some issues with the bfd libs though. Anyone use > something different or better that is known to work with the latest tools? If you have a BBA dcload-ip is absolutely the way to go. It's not exactly the easiest thing to build because it requires that libbdf from sh-elf be installed and then you have to edit the Makefile.cfg for dcload to point to the installed location of that lib/include. The other thing that might be useful for you to change in the Makefile.cfg is the IP of the Dreamcast. There is one other BBA loader that I can think of off the top of my head, but AFAIK it's totally unmaintained (not to mention dcload is much more robust in comparison.) Anyways the loader I'm thinking of is IP upload slave (http://mc.pp.se/dc/ipslave.html) which was one of the first Dreamcast BBA loaders. Attached is a Makefile.cfg that worked for me on a Linux machine that I used buildcross with. You'll probably still need to edit it a bit, but it should be much closer to what you need. |
From: Caleb C. <cal...@gm...> - 2010-12-22 19:05:45
|
Lawrence - Running "./buildcross -dc -k" did the trick! After the build completed I ran the "environ.sh" and was able to build the "hello" project under the "examples" folder. Thank you guys for helping get this working. In case anyone else is looking to get this working in a Windows environment and is wondering what could work for them, I am running: - Windows 7 Ultimate (64bit) - Cygwin (Setup.exe version 2.738) - buildcross 1.8 (pulled from git head at https://github.com/losinggeneration/buildcross.git) Now I am just trying to find a way to test code. It seems the best way is to just send the elf over the network to the dc using "dcload-ip" correct? I pulled down the latest one (1.0.4 from 2003) and am trying to get it built now. Running into some issues with the bfd libs though. Anyone use something different or better that is known to work with the latest tools? ~Caleb On Wed, Dec 22, 2010 at 9:43 AM, Harley Laue <los...@gm...>wrote: > ./buildcross dc -k |