Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
104 user(s) are online (54 user(s) are browsing Forums)

Members: 1
Guests: 103

kishigo, more...

Headlines

Forum Index


Board index » All Posts (Rogue)




Re: Hyperion blog update.
Quite a regular
Quite a regular


@Hans

No, I don't mean sizes are adjustable. I'm not sure were I saw this, but I recently came across a PCI card with a 64 bit BAR that was pretty large. I thought it was a graphics card, but come to think of it I am no longer sure (although I wouldn't know of any other cards that have such large BAR's).

Must be getting old, I can't remember what is was, dammit :(

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: Hyperion blog update.
Quite a regular
Quite a regular


@QuikSanz

You cannot "just" map the graphics card area, since there are going to be implications (especially with caching and read/write coherency) but it might offer a way to access large areas of graphics cards that do have a 64 bit address space.

It's mandatory that the CPU could access that memory, though. To be honest, I don't know how modern graphics cards like NVidia or RadeonHD do that; but I had previously seen the P-10 and a few other cards that could have 64 bit BAR's that the CPU could access.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: Hyperion blog update.
Quite a regular
Quite a regular


Alright, let me try to answer a few of the questions.

1) There is no limit on the maximum size of the ExtMem blob. It just needs to fit in the physical memory.
2) Currently, nothing enforces sharability of the memory, since there is no per-task MMU setup yet. Rules for that will be laid out later. Right now the rule is that tasks and sub-tasks can share the memory.
3) Memory in ExtMem objects is currently not subject to swapping, but there isn't a reason it cannot be swapped.
4) ExtMem works with both 32 and 64 bit CPU's. It theoretically works on the classic too, but you rarely have enough memory on the classic for something like that.

About remapping, I plan to add that ASAP. Remapping means that the offset into the ExtMem blob changes without the virtual address window changing. As was rightly pointed out, finding virtual address space for a map isn't free, so re-setting the start address into the blob is an optimization that will be useful.

Another point I haven't raised in the blog (yet) is how this can evolve. Right now, there are three possible ways to map the pages for the blob: Immediately (meaning the whole memory is allocated when the blob is created, for performance reasons), by mapping (meaning once a range is mapped for the first time it is stacked up with pages), or by access (meaning no pages are allocated until they are really accessed). Each of these methods is successively more expensive at runtime in favor of being more efficient with pages.

There is more that can be done with the system once it evolves. For example, it would be possible to not even have memory backing up the blob. Mapping a range could mean memory-mapping a file, and unmapping would write the file back to disk (or buffer in a memory buffer until a commit writes it back), to allow for easy memory-mapped files. Another example is mapping a large graphics card area. Right now, you are limited to the size of the PCI address space; graphics card drivers will make sure the right stuff is copied in the right addresses. However, ExtMem could be used to access the memory directly for cards capable of 64 bit PCI access, which would be interesting for things like Compute shaders that might need to work on a large dataset.

As you can see, we do believe that there is potential for future functionality in this. We won't be able to make AmigaOS a 64 bit OS any time soon, as I wrote on the dev blog; the 32 bit pointers are depply woven into the API, and only by throwing the whole API away and replacing it with a new one would this be cured. But at the very least, this allows for using much more memory than we have right now, and the performance overhead, while not being zero, is relatively low.

Hope that answers some questions.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: Solved why Timberwolf won't launch, DSI error.
Quite a regular
Quite a regular


@Fairdinkem

Quote:
Yeah I have no idea why they didn't make it a stand alone installer?


Not intentionally, these must have been overlooked during packaging. Which is... weird. I'll have a look as soon as I find the time, and make a new archive.

Thanks a lot of the the info, very helpful!

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Timberwolf, Warp3D and ARMA
Quite a regular
Quite a regular


Allow me to say a few words on the topic. Everything I say here is my personal opinion/perception. I do not represent either Hyperion nor A-Eon, and I would like this to be understood. It should be obvious, but the past has taught me

Timberwolf's situation is pretty bad, and I can understand that people are upset. It's been a while since there was any sign of life from it, and clearly this cannot go on like this. We're working on a solution for the situation, and I hope we will be able to say more real soon. I can't say more on this at this point.

On the topic of Warp3D: It was pointed out to me in a mail that I obviously give more time to ARMA than to the Amiga. It's funny that you should mention this game. As some of you may or may not know, the third installment of the series was announced in 2011, to be released in early 2012. Unfortunately, things didn't quite work out of the company, and now, in 2013, the game is still unreleased (a public beta is available, but the release date has been set to the 12th of September).

As you most likely already figured out, I am a big fan of the game. So after it was now delayed for over one and a half year, we had to find out that a lot of features we had been looking forward to got axed from the game. Long delay, plus axed features, I wasn't happy. I was pretty disappointed. But I did not feel betrayed. It's a product, not a marriage. The team fell on pretty hard times. Such is life.

Back to Warp3D. The situation there is pretty much the same. Announced with a release date that couldn't be kept. And likewise, it's a product. Not a marriage, or a vow, or any such thing. Products get delayed. Sometimes even canceled. Features get axed. New features get added. While I can understand the disappointment, I do not understand that people tend to make a big deal about it. Someone referred to it as “waiting hell”. I beg your pardon? It's not like you are waiting for an oxygen mask on a decompressed plane. It's just a product. Don't make more out of it.

So, a product that got delayed. One of the reasons is that I had initially deemed the task easier than it is. My original idea was to work on the RadeonHD 45xx, which is covered to a certain extend by the documentation. The Evergreen series isn't. It turned out that a lot of things are quite different. I had done Warp3D driver before; I had done the initial Virge and Voodoo drivers (although Thom did the bigger part of the work on the Voodoo), I wrote the R100 and the R200 drivers. Evergreen is a different beast.

Another issue is timing. Different setups, depending on the maker or the BIOS revision of the card, make life quite a bit more difficult. And the codebase is huge. Just to give you an idea, the function that generates the pixel shader from the Env Combiners is almost twice the size as the entire compositing code in the RadeonHD driver. The shaders can get to half a kilobyte of code, and more.

Also, I had to share the time with the work on Gallium. There is a certain synergy between those, but not too much. Gallium is one of these projects where you try to balance a load of things that sometimes contradict each other: A model that is Amiga-like enough to serve as a system library, it has to be low-level enough to be able to work with nothing but bitmaps, needs to be re-entrant, needs to be thread-safe, needs to be multicore capable, and it needs to be able to load some other driver than a Gallium based one. All of this takes time, especially if you are trying to do it in such a way that you don't create a situation that will result in a support nightmare – you want something that can grow along with the rest, not hold anything back.

Now, if you are looking for dates or estimates, I won't give them. It's proven to be unreliable anyway. It will be done, when it's done.

Finally, something more personal. Things haven't been easy in the last couple of years. The Amiga had been my hobby for a long time, but as with so many things, once they become work, they stop to be a hobby. Also, the trench fighting in the Amiga community was getting to me, and it was better to just leave. What bothered me most wasn't necessarily the difference of opinion but rather the attempts, from both sides, to make life more difficult for the other. Oh, yeah, and there was this big-ass lawsuit, and the numerous attempts to cash in on the work we've done. Once it comes to this, you're better off far away from it all.

I don't believe in religion, but if there was a reincarnation, I would know one thing that I would change - never step into the spotlight. It doesn't do you any good, it just means you are visible for everybody to take cheap shots at. Like with actors, people tend to not see the person but rather the work. Stick with a nickname, and never let the real you come out. You'll regret it. I know I do.

One more thing, I haven't read any Amiga sites in years and I do not plan to change that, so if you feel you want to say something, I will most likely not read it. If you feel you have something important to say to me, feel free to write me an email (No Pm's, I don't read them) - unless it's "f*** off", I heard that enough.

And apologies for the length of this.


Edited by Rigo on 2013/8/22 23:12:53
Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: Ban the uploader
Quite a regular
Quite a regular


Quote:

kas1e wrote:
:)) now i think its time to make a lawsuit :) Or repeat the same on 5 more pages :)


I fail to see what is funny about it. What is being discussed here is the fundamental disrespect for ownership/copyright. It seems to be a prevalent notion for some people that they are entitled to have/get something. That isn't the case. The author of a piece of software, unless he explicitly waives it, has all the rights to his work, and nobody else has the right to distribute his work without the author's permission.

Unfortunately, the predominant mindset seems to be that everything is free if it can be obtained from somewhere. That is not true. Nobody is entitled to get something if the author chose to withhold it, and only the author as the rights to upload his work unless he explicitly states otherwise.

Come on, folks. Show some respect.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: The Revenge of the Qt Demo Browser
Quite a regular
Quite a regular


Quote:
Still, Qt is just a hawk for resources, both CPU and memory wise, so it is never possible to achieve lightning speed.


I wonder why this is the case. It was designed for mobile devices, it should be possible to run faster... did you ever profile it to see where the time goes?

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: Lack of progress
Quite a regular
Quite a regular


Quote:

Elwood wrote:

There was a speed increase in one of the versions of FF. It will certainly help with the speed issue.


IIRC, the later versions also used significantly less memory than 4.0.1

Plus, I finally want to use AdBlock again :)

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: radeonHD video hw acceleration
Quite a regular
Quite a regular


Quote:

Hans wrote:

Interestingly, the R200 entry on wikipedia claims that it can handle up to 6 textures per pass via some "loop-back" technique. I have no idea what the restrictions are, but it could still be doable. If not, then it should still be able to handle YUV422, as that requires just one texture. Plus, they have overlay.


Hm, true... there are six texture address registers. I do seem to remember that I looked at the YUV support and there was something stopping me from doing it, but seriously, I can't remember what it was... :|

Quote:
Radeon HD cards have 4 or more texture units (depending on the series), which is enough for separate Y, U, and V textures plus an alpha mask. That will cover planar YUV modes. I already have example shader code for this, although it will have to be adapted.

Radeon X1000 (R500) series cards also have 4 or more texture units, but I'll probably stick to the Radeon HD series only (almost no one uses the Radeon X1000 series, and there are so many other things to spend time on).


Agreed. X1000 radeons where nice cards but it will be hard to even find them anymore.

Luckily, the shaders allow for a lot of things to be done within the chip, so converting YUV to RGB is "easy" to do on the RadeonHD (in quotes, because I still shudder at seeing the xv shader code in the ati video driver )

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: Will IBrowse v2.5 ever be released?
Quite a regular
Quite a regular


Quote:

Swoop wrote:
Quote:
Rigo wrote:
Time and money is better spent on Timberwolf, where there are good chances of getting something from this decade.

The Problem is, I can't currently run Timberwolf.
I have to re-save the appdir entry, and bookmarks don't work on my A1XE-G3 800.


I don't want to turn this thread into a Timberwolf bug report thread, so just as a heads-up, I hope you have reported this issue elsewhere.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: Will IBrowse v2.5 ever be released?
Quite a regular
Quite a regular


Quote:

Elwood wrote:
@ChrisH

Quote:
when it is optimised.

I don't know the future so I would say: "if it will be optimised"


I am not quite sure why you felt this comment was necessary to be honest.
Hardware rendering is planned for Timberwolf once Gallium is ready, since there is an OpenGL-Based layer manager for Firefox. Trying to write a new one from scratch is quite a bit of work, prone to errors, and becomes outdated quickly.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: radeonHD video hw acceleration
Quite a regular
Quite a regular


Note that most Radeons actually support one or the other form of YUV textures, but support for that was never included in Warp3D. It's difficult to retrofit it into the compositing code since that would only work under certain contraints. The R200 for example can use separate YUV plane data but only when using the full three texture units. That means there is no room for a separate alpha map, so things would need to be done in multiple passes with temporary bitmaps.

Here's hoping we can support more of that stuff on the later chips, with Gallium there is certainly better chances to see this working.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: Elite Dangerous
Quite a regular
Quite a regular


Quote:

ChrisH wrote:
@amigacooke
According to KickTraq's *projection* (not the misleading "trend"), it may get as little as £0.9 million by the deadline, which is far below the necesary £1.2 million. That means it would need a huge last minute "surge" to make-up the shortfall


I recently pledged on my first crowd funding project, Star Citizen by Chris Roberts. For a long time it looked like their 2 million dollar goal would be impossible to reach, and they ended up with almost 7 million on their final day of funding. Traditionally, a lot of people wait until the very end to invest.

I am pretty sure Elite will make it.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: Timberwolf RC3 available
Quite a regular
Quite a regular


Quote:

Younghippie wrote:
I understand that if the Friedens have not time to create a new RC, but they have a liability towards the people who payed for the bounty. I think a litte bit of information what we can expect or not for the next weeks won't be too much.


Are you one of the donators? If yes, then I apologize, otherwise demanding something is a bit big, don't you agree?

Anyway, there won't be much changes in Timberwolf anymore, so much was clear. Hardware acceleration will wait until 4.2, the only thing that will still be coming is bug fixing. Thom's hospitalization has made things go slow, and in fact, he was still recovering from it up to this week.

We'll be trying to wrap this up before the end of the year. Until then, I think the current RC is pretty much usable as it is.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: AmiWest 2012 News?
Quite a regular
Quite a regular


Quote:

vox wrote:

Point is that RadeonHD transition is biggest step forward, but it is sad indeed that all those who basically got SAM 460 and X1000 for RadeonHD (4000 series) will have to suffer with further 2D only.


Suffer? Don't you think that's a bit melodramatic?

Quote:
As well as those who jump to RadeonHD 6000 now, sice driver development is assured, but no Warp3D implementation yet.


Your point... being?

Quote:
This also sounds like a quick "adjust to the avail resources" thing way more then a plan - it would sound better if first RadeonHD 2D driver supported 6000 series and 4000 was never sold as according card. No current Amiga reseller sells this card too. Now, we just have to adjust.


Again, what is your point? Yes, Warp3D support for these cards was never planned. Yes, due to delays with the OS A-Eon decided to fund these drivers as a stop-gap solution. What is your problem with that? I am quite sure that if you had a supported card, you would be singing quite a different song. As I said before, this is not a loss for those with 4000, but a win for those with 5000/6000.


Quote:
Yes, if it would be an opened bounty with set goal.
These cards are getting unavail, but are not bad at all.
And you see that merely all current SAM 460ex and X1000 users feel kind of betrayed with this kind of decision, even its all your good work and we all need to be grateful for your hard work.


Speak for yourself but not for "all current SAM 460ex and X1000 owners". You are blowing tings up beyond proportions. Calling this a "betrayal" is bollocks.

Quote:
However, I do agree its easier to get new card with assured 3D driver existing then waiting for development, if we have clarification that OS 4.2 Gallium will support 3D with these cards too.


You will never get any guarantee. Once Gallium is available, we'll post a list of supported graphics cards. That will ALMOST CERTAINLY include the 4000, 5000, and 6000 series, and possibly beyond that, but the exact list you'll get once we know it.

Quote:
OK, more progress reports and avail betas. There is nice infrastructure and surely it keeps community alive and bugfixing possible.


We have beta testers for beta testing. There is no point in doing a public beta test, this will always generate more noise than signal. Our beta testing works well enough for that. Public beta tests open a can of worms. You tell people explicitly not to use it if they have important data, and still they do and then complain when something was lost.

No thanks.

Quote:
Once on subject, when we will know what should be new elements of AmigaOS 4.2? No release date promised.


You'll hear it when we say something.

Quote:
2D / 3D driver for AmigaOS hasn`t anything to do with AmigaOS?


Not the point. I said, Warp3D drivers are an A-Eon project, I am not talking about anything else and you know that.

Quote:
Please either take all development in house, or accept 3rd party developments that become parts of AmigaOS should be supported to some extent.


3rd Party development was always part of AmgiaOS. Picasso96? Roadshow? Warp3D? These are all external components that are now integrated into AmigaOS. I don't see what is wrong with that.

Quote:
This kind of bad relations to users comes from "flipping the ball to other corner" - that is Acube hardware (but we use Hyperion OS on it), that is A-EON, these we develop as Amiga bounty etc.


Show of hands please: Who thinks our user relationship is bad?

I am actually not quite sure what you mean here. Of course it is ACube hardware, and you can actually use a non-Hyperion OS on it (Linux). The stock PC hardware is not done by Microsoft. And here's the surprise: Hardware drivers on Windows are not done by Microsoft either. Surprised?


Quote:
With 3-5 gfx cards and 3-5 sound cards supported?


How much programming knowledge do you actually have? Is it enough to make a qualified assumption? And it isn't 3-5 graphics cards. Let me summarize it for you:

Cedar
Redwood
Juniper
Cypress
Hemlock
Palm
Sumo
Barts
Turks
Caicos

These are the graphcis cards that the RadeonHD Warp3D driver currently supports. I count 10.

We're working on this as good as we can, but there are limits. It's unfortunate we have to sometimes branch off into different directions, or adjust plans to suit a new situation. But that cannot be changed.

So yes, it is damn hard, and don't you dare suggest anything else. You're insulting all the developers working on this and giving it all they can.

Quote:
It seems that real use of PCI and PCI-E cards will be a weak knee of anyone that isn`t Microsoft. Or that dont have Linux community size development.


Old news, friend. Even Linux struggles to support more exotic hardware. It will always be like that, but that is not a big issue. Yes, you cannot use an NVidia card under OS 4, so what?

Quote:
Well if you look towards the future, you could drop Radeon 9000 series support and make a PCI-E 2 PCI converter for older boards of find a RadeonHD that can work in AmigaOnes, Pegs and SAM 440.


Gallium will not support these cards. You can already use PCI versions of RadeonHD's in most systems (although I think the Pegasos II firmware barfs on graphics cards behind a PCI2PCIE bridge)

Quote:
And it looks like it will never be. My gentle suggestion is that Hyperion / A-EON / Acube could have someone that would communicate politely, with much patience and culture to community - press releases or forums. You guys do have both much work to do and heavy stance that your choices are simply the best that allow no room for any second opinion.


I have been very patient with you, and have not been impolite as far as I can see. This is the communication you will get. The alternative is no communication at all. The problem is not the way of communication, but the fact that you don't want to hear what we have to say. It doesn't matter how it is said, the facts will not change.

Quote:
That is the biggest news of Amiwest and this year to my belief (let me know if there was something more important at least in software). Some idea of system requirements would be nice. Better who is doing the development (one person, team ...) and is any public release planned for first year of development?


System requirements: When it's done. There is no way to tell beforehand.
Who does it: Why does it matter? It will be done when it's done.

You see, you demand knowledge that nobody is willing or able to give you. You got a news item on AmiWest. Take it for what it is, a piece of news. There is no need nor requirement from A-Eon or anyone else to put any more information to this. Any additional information will be released as it becomes available or as the developers seem fit. IF anybody intended to say something about the team size or system requirements, it would have been in the release, but there is no such thing.

Officially Libre requires 512MB RAM.

Quote:
God thanks the Warp3D software emulation that allows SAM 460 and X1000 users to have some joy.


As others have already pointed out (and I am an atheist anyway), God doesn't have anything to do with it. And the reason there is a software emulation possible for Warp3D is because Sam Jordan, Thomas Frieden, and myself actually did this. This is a typical display of the "wanna have" attitude.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: AmiWest 2012 News?
Quite a regular
Quite a regular


Hans has basically already said everything there is to be said about this. It was clear from the word go that the subset of cards that could be supported by the drivers are limited. The 4000 is almost impossible to buy now, they may be on E-Bay, but a new 5xxx costs you somewhere in the 20-30 Euro range, so seriously, that was not even worth considering.

There are some subtle and some not-so-subtle differences in the older and newer cards. If we had picked the older cards for support, then the current discussion would revolve around the keywords:

"Outdated"
"Unable to obtain"
"But I don't have one"
"Why not 5000/6000"

This way, they just revolve around other keywords.

Saying that no one uses 5000/6000 is wrong, they are probably equally much used as the 4000. You'll be able to get one for a mere 20-30 Euros.

Seriously, can we put this discussion to rest? No ranting will change the fact. The drivers will support the Evergreen series; adapting them to other cards is going to be work that might not be worth the effort. The Warp3D drivers will come out "as is", if you have a 4000 and don't want to upgrade, fine, you'll have to wait for 4.2.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: AmiWest 2012 News?
Quite a regular
Quite a regular


Quote:

vox wrote:

3D is never mentioned here, but kind of rethorical question is 2D support only real driver?


3D is never mentioned because this announcement was about 2D drivers. Do you think those write themselves, especially with things like Compositing in the graphics kernel?

But that is the poinr. You are drawing conclusions that aren't there, there is explicitly no mention of 3D.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: AmiWest 2012 News?
Quite a regular
Quite a regular


Quote:

vox wrote:

If a delay has been made, about time near of promised, just say project is ongoing but will be delayed for six months or so.


Please lose the word "promised". I hate it that people always try to put it as if we promised something and didn't make it. We don't make promises. We have release plans that might or might not make it. There is a difference between that and a promise.

About announcing delays, most people don't do it since any release date is a guess at best.

Quote:
RadeonHD Warp3D driver might be giving what wasnt expected (so it might be seen as bonus) but as far as it doesnt support existing cards bundled with AmigaOne systems, its an upgrade requirement, not support.


Whoever said it was support? Nobody claimed that. It's not even a Hyperion project, and as such, doesn't have anything to do with AmigaOS.


Quote:
Is it really so hard to both support existing and make path towards future?


You have no idea.

Quote:
Thanks to Trevor and Hyperion, but still there is a room for improvement, so out of criticism, what should be seen as positive criticism could be taken into account.


You are mistaken. There is no room.

Quote:
Also, LibreOffice port deserves really some more room and clearance.


What about "X is porting Y" needs clearance? Release date? Not going to happen. System Requirements? Too early. What do you expect, seriously?

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: AmiWest 2012 News?
Quite a regular
Quite a regular


Quote:

vox wrote:
If Warp3D driver is stop gap, and Gallium will surely include 9000, HD 4000 cards then it should be said temporarily we do effort to support most modern cards and since that driver release, X1000 and SAM460 are offered with such cards. Assuming that could be the point.


Gallium will not support any Radeon 9000 based card. It requires pixel shaders 2.0 or better, and the 9000 don't have that.

The point in supporting the current HD5xxx and HD6xxx is simply because these cards can still be obtained from a normal store.

Quote:
Community is small, some competition still exists, but it seems some clear path of progress and small updates would satisfy most of community, including users and supporters and competition of any kind. The same applies to MorphOS and AROS just as well.


So far, there has been no change of plan in what will entail 4.2, so I don't really see where that path is not clear enough. I also don't see why people try to draw negative vibes out the Warp3D announcement. It just adds something that you didn't even expect to get before.

Seriously, what's the problem here? Delays? They will always happen. They happen in big-budget companies as well as with no-budget companies, and everything in-between. I am a big fan of the game ARMA, and I was thrilled last year when they announced part III. In the meantime, their projected release date ("Summer 2012") has come and gone. Their schedule for the alpha release has been extended to end of the year. Am I disappointed? Of course I am. Do I say they have broken some promise? No, because these things just simply happen.


Edited by Mikey_C on 2012/10/26 13:41:11
Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top


Re: AmiWest 2012 News?
Quite a regular
Quite a regular


Quote:

ChrisH wrote:
@Rogue Quote:
That is, unfortunately, not always possible.

We need to be highly adaptive,

I'm afraid that I don't understand your answer, but also appreciate that you may not be able to say more either.

Although I wondered if your "highly adaptive" could have been a hint that Hyperion doesn't always know (in advance) when some people will be able to work on a project, in which case some delays could be due to people not being able to work on a project as much as was expected. If that is so, that I really don't see the harm in saying so.


Ah, the joys of writing. There's the trouble, I can never tell how my words will be interpreted.

No, what I meant is that we need to be able to adjust to the situation. The new Gallium/Mesa release is such an example; I'd rather let it rest for a month until the final version of 9.0 is out than try to work with a developer release only to find that something substantial has been changed.

Hope that's clearer.

Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Go to top



TopTop
(1) 2 3 4 ... 27 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project